Pardus Testing Team
Erkan Yilmaz (Talk | contribs) (→Before Reporting Any Bugs: sadece link eklendi: [http://www.ozgurlukicin.com/forum/pardus-2008-test-takimi/ Pardus 2008 Test Team] (Turkish language) - interwiki link yok) |
Erkan Yilmaz (Talk | contribs) (just typos + formats (for not interfering in current testing philosophy)) |
||
| Line 1: | Line 1: | ||
== Pardus Testing Team == | == Pardus Testing Team == | ||
| − | For every product or service that | + | For every product or service that is produced by human beings, it is inevitable to contain bugs or errors. That's why quality assurance policies are needed for every product to decrease the rate of malfunctions. |
| − | The aim of Pardus Testing Team is to minimize the rate of malfunctions before | + | The aim of the Pardus Testing Team is to minimize the rate of malfunctions before and after the releases. Another aim is to support the fixing of bugs as soon as possible. |
== Contribution == | == Contribution == | ||
| − | Free Softwares are not developed and maintained by only the developers but also by the people who | + | Free Softwares are not developed and maintained by only the developers but also by the people who volunteer to make translations, help bug-fixing, test, contribute in terms of graphics and package the software. Testing is a good starting point to begin to contribute to free software as it does not require much technical information and besides, helps in learning the softwares that are being tested. |
| − | == How Can I Be a Member of Pardus Testing Team == | + | == How Can I Be a Member of Pardus Testing Team? == |
| − | We are expecting you to isolate the testing environment from your daily usage. You can ensure this via virtual machines, for testings inside Releases(packages, interim releases..etc.) However for testing the actual releases, testings before the releases, you definitely need a machine dedicated to this job. | + | We are expecting you to isolate the testing environment from your daily usage. You can ensure this via virtual machines, for testings inside Releases(packages, interim releases..etc.). However for testing the actual releases, testings before the releases, you definitely need a machine dedicated to this job. |
| − | Besides; you are expected to have basic skills of knowledge about Linux and Pardus. Although you are not expected to have a developer level of knowledge, questions like "What is your wireless card's name and its' vendor id?", " | + | Besides; you are expected to have basic skills of knowledge about Linux and Pardus. Although you are not expected to have a developer level of knowledge, questions like ''"What is your wireless card's name and its' vendor id?"'', ''"Can you add the repo at the address xxxxxx, and then upgrade the system?"'' should not sound unfamiliar to you. |
| − | You must register every computer you are going to use by filling the form at [http://cekirdek.pardus.org.tr/~serbulent/ptg_bilgi.ods this address] and then send it to psts{{at}}pardus.org.tr. | + | You must register every computer you are going to use by filling the form at [http://cekirdek.pardus.org.tr/~serbulent/ptg_bilgi.ods this address] and then send it to psts{{at}}pardus.org.tr. A completed form can be seen ''[http://cekirdek.pardus.org.tr/~serbulent/ornek.ods here]''. |
| − | == How are the things going on for Testing Team before a Pardus Release == | + | == How are the things going on for the Testing Team before a Pardus Release? == |
Before every main release, a form is sent to the Pardus Testing Team Members, and they provide hardware information of the machines which they plan to use as a testing machine. For every system a number is assigned. | Before every main release, a form is sent to the Pardus Testing Team Members, and they provide hardware information of the machines which they plan to use as a testing machine. For every system a number is assigned. | ||
| Line 23: | Line 23: | ||
With every testing release, Pardus Testing Team Members make a fresh installation and fill in the form they are provided according to the test results in the form. After that, they send these forms to the tester list when the forms are wanted. | With every testing release, Pardus Testing Team Members make a fresh installation and fill in the form they are provided according to the test results in the form. After that, they send these forms to the tester list when the forms are wanted. | ||
| − | If any bugs appear, they are entered to | + | If any bugs appear, they are entered to [http://bugs.pardus.org.tr bugzilla] (the bug tracking system for Pardus) and can be tracked by the reporter and the Testing Team Responsible till the bug is closed. |
| − | Pardus Testing Team Members answer to the feedbacks from Testing Team Responsible in a certain period of time and keep on doing these things till the stable release is announced. | + | Pardus Testing Team Members answer to the feedbacks from the Testing Team Responsible in a certain period of time and keep on doing these things till the stable release is announced. |
====Reporting Before Release Tests==== | ====Reporting Before Release Tests==== | ||
| − | After the release announcement, Pardus Testing Team starts testing with the help of the guide they are provided. | + | After the release announcement, the Pardus Testing Team starts testing with the help of the guide they are provided with.<br> |
| − | The succesful steps are signed as | + | The succesful steps are signed as: |
1.1 Yes<br> | 1.1 Yes<br> | ||
| Line 36: | Line 36: | ||
1.3 Yes<br> | 1.3 Yes<br> | ||
| − | but the steps that are failed should be written in | + | but the steps that are failed should be written in detail as much as possible and be added to the final report. The final report is send to the tester list via e-mail as a "plain-text" . The header of the post should be in the form of "Test No:NN Sistem-XXX" . |
| − | ==How about the Tests during a Release== | + | == How about the Tests during a Release? == |
| − | Tests during a Release | + | Tests during a Release are different from Before-The-Release Tests as this kind of tests start at the beginning of the new stable release and go on till the release is maintained officially. That kind of Tests are seperated into two groups: |
| + | *"Upgrade Tests" and | ||
| + | *"Function Tests" | ||
====Upgrade Tests==== | ====Upgrade Tests==== | ||
| − | For that kind of testing mechanism, you should have a freshly installed version of both the stable release ( e.x. Pardus-2007 ) and interim versions of this release ( e.x. 2007.1 , 2007.2 , 2007.3 ). After every Test process, as we are going to need a fresh version of these installations, installing these systems as a virtual image (e.x. using VirtualBox) is useful for your own health :) We are going to use these images in update tests. | + | For that kind of testing mechanism, you should have a freshly installed version of both the stable release ( e.x. Pardus-2007 ) and interim versions of this release ( e.x. 2007.1 , 2007.2 , 2007.3 ). After every Test process, as we are going to need a fresh version of these installations, installing these systems as a virtual image (e.x. using VirtualBox, see [[HOWTO:VirtualBox]]) is useful for your own health :) We are going to use these images in update tests. |
Besides, we need another virtual image that is periodically upgraded from the stable repository after every repo updates. | Besides, we need another virtual image that is periodically upgraded from the stable repository after every repo updates. | ||
| − | The Process generally works in that way: Testing Team Responsible starts an ACK process for the packages waiting in testing repository. The packages that receive ACK from the developers are merged to the current stable repository and to a temporary repository consisting of newly ACK'ed packages. Freshly installed releases are given the address of this temporary repository and being upgraded from this repository. | + | The Process generally works in that way: the Testing Team Responsible starts an ACK process for the packages waiting in the testing repository. The packages that receive ACK from the developers are merged to the current stable repository and to a temporary repository consisting of newly ACK'ed packages. Freshly installed releases are given the address of this temporary repository and being upgraded from this repository. |
| − | Every upgraded release is being tested after restarting the system, in order to learn whether system is capable of doing basic things or not. After this, it is checked with ''revdep-rebuild'' command to control if any broken distributed library files in reverse dependencies are missing. | + | Every upgraded release is being tested after restarting the system, in order to learn whether the system is capable of doing basic things or not. After this, it is checked with ''revdep-rebuild'' command to control if any broken distributed library files in reverse dependencies are missing. |
====Function Tests==== | ====Function Tests==== | ||
| Line 60: | Line 62: | ||
| − | After you make an installation once on a virtual machine such as VirtualBox, you can take a screenshot of your machine every time you upgrade it to the latest version of the stable repository, so that you can use this image(screenshot) for your upcoming tests. That prevents installing the same packages every time you use a machine upgraded to the latest version of the repository. | + | After you make an installation once on a virtual machine (such as VirtualBox - more at: [[Virtualization:Contents]]), you can take a screenshot of your machine every time you upgrade it to the latest version of the stable repository, so that you can use this image(screenshot) for your upcoming tests. That prevents installing the same packages every time you use a machine upgraded to the latest version of the repository. |
| − | The upgraded release is being tested after restarting the system, in order to learn whether system is capable of doing basic things or not. After this, it is checked with revdep-rebuild command to control if any broken distributed library files in reverse dependencies are missing. | + | The upgraded release is being tested after restarting the system, in order to learn whether the system is capable of doing basic things or not. After this, it is checked with ''revdep-rebuild'' command to control if any broken distributed library files in reverse dependencies are missing. |
| − | As testing all the characteristics of the programs and the libraries by the Members of Pardus Testing Team isn't possible in terms of knowledge, experience and time; the packages are classified in 3 categories: [[ | + | As testing all the characteristics of the programs and the libraries by the Members of Pardus Testing Team isn't possible in terms of knowledge, experience and time; the packages are classified in 3 categories: |
| + | *[[Packages to be tested in details]] | ||
| + | *[[Packages to be tested in normal standards]] and | ||
| + | *[[Packages to be tested only in installation]]. | ||
====Testing Repository Adresses==== | ====Testing Repository Adresses==== | ||
| − | For Pardus 2007 : http://paketler.pardus.org.tr/testci-2007/pisi-index.xml.bz2 | + | *For Pardus 2007 : http://paketler.pardus.org.tr/testci-2007/pisi-index.xml.bz2 |
| − | + | *For Pardus 2008 : http://paketler.pardus.org.tr/testci-2008/pisi-index.xml.bz2 | |
| − | For Pardus 2008 : http://paketler.pardus.org.tr/testci-2008/pisi-index.xml.bz2 | + | *For Pardus 2009 : ''to be added'' |
== Before Reporting Any Bugs == | == Before Reporting Any Bugs == | ||
| − | * If you get an installation error, check sha1sum of the image you have downloaded. Burn the CD at DAO mode and at most 16x speed and check your CD is OK. | + | * If you get an installation error, check sha1sum of the image you have downloaded. Burn the CD at DAO mode and at most 16x speed and check if your CD is OK. |
| − | * When you get an error, try to understand the error message. Be sure that reason of the problem isn't your program settings. Do not forget that [http://www.google.com Google is your best friend | + | * When you get an error, try to understand the error message. Be sure that the reason of the problem isn't your program settings. Do not forget that [http://www.google.com Google] is your best friend. |
* Try to repeat the GUI errors by starting the program from console. Attach the error log from the console to your error report. | * Try to repeat the GUI errors by starting the program from console. Attach the error log from the console to your error report. | ||
| Line 86: | Line 91: | ||
[[tr: Pardus Test Gönüllüsü Olmak]] | [[tr: Pardus Test Gönüllüsü Olmak]] | ||
| + | [[Category:Pardus]] | ||
| + | [[Category:Tests]] | ||
Revision as of 21:12, 19 January 2009
Contents |
Pardus Testing Team
For every product or service that is produced by human beings, it is inevitable to contain bugs or errors. That's why quality assurance policies are needed for every product to decrease the rate of malfunctions.
The aim of the Pardus Testing Team is to minimize the rate of malfunctions before and after the releases. Another aim is to support the fixing of bugs as soon as possible.
Contribution
Free Softwares are not developed and maintained by only the developers but also by the people who volunteer to make translations, help bug-fixing, test, contribute in terms of graphics and package the software. Testing is a good starting point to begin to contribute to free software as it does not require much technical information and besides, helps in learning the softwares that are being tested.
How Can I Be a Member of Pardus Testing Team?
We are expecting you to isolate the testing environment from your daily usage. You can ensure this via virtual machines, for testings inside Releases(packages, interim releases..etc.). However for testing the actual releases, testings before the releases, you definitely need a machine dedicated to this job.
Besides; you are expected to have basic skills of knowledge about Linux and Pardus. Although you are not expected to have a developer level of knowledge, questions like "What is your wireless card's name and its' vendor id?", "Can you add the repo at the address xxxxxx, and then upgrade the system?" should not sound unfamiliar to you.
You must register every computer you are going to use by filling the form at this address and then send it to psts
pardus.org.tr. A completed form can be seen here.
How are the things going on for the Testing Team before a Pardus Release?
Before every main release, a form is sent to the Pardus Testing Team Members, and they provide hardware information of the machines which they plan to use as a testing machine. For every system a number is assigned.
With every testing release, Pardus Testing Team Members make a fresh installation and fill in the form they are provided according to the test results in the form. After that, they send these forms to the tester list when the forms are wanted.
If any bugs appear, they are entered to bugzilla (the bug tracking system for Pardus) and can be tracked by the reporter and the Testing Team Responsible till the bug is closed.
Pardus Testing Team Members answer to the feedbacks from the Testing Team Responsible in a certain period of time and keep on doing these things till the stable release is announced.
Reporting Before Release Tests
After the release announcement, the Pardus Testing Team starts testing with the help of the guide they are provided with.
The succesful steps are signed as:
1.1 Yes
1.2 Yes
1.3 Yes
but the steps that are failed should be written in detail as much as possible and be added to the final report. The final report is send to the tester list via e-mail as a "plain-text" . The header of the post should be in the form of "Test No:NN Sistem-XXX" .
How about the Tests during a Release?
Tests during a Release are different from Before-The-Release Tests as this kind of tests start at the beginning of the new stable release and go on till the release is maintained officially. That kind of Tests are seperated into two groups:
- "Upgrade Tests" and
- "Function Tests"
Upgrade Tests
For that kind of testing mechanism, you should have a freshly installed version of both the stable release ( e.x. Pardus-2007 ) and interim versions of this release ( e.x. 2007.1 , 2007.2 , 2007.3 ). After every Test process, as we are going to need a fresh version of these installations, installing these systems as a virtual image (e.x. using VirtualBox, see HOWTO:VirtualBox) is useful for your own health :) We are going to use these images in update tests.
Besides, we need another virtual image that is periodically upgraded from the stable repository after every repo updates.
The Process generally works in that way: the Testing Team Responsible starts an ACK process for the packages waiting in the testing repository. The packages that receive ACK from the developers are merged to the current stable repository and to a temporary repository consisting of newly ACK'ed packages. Freshly installed releases are given the address of this temporary repository and being upgraded from this repository.
Every upgraded release is being tested after restarting the system, in order to learn whether the system is capable of doing basic things or not. After this, it is checked with revdep-rebuild command to control if any broken distributed library files in reverse dependencies are missing.
Function Tests
For the Function Tests, the actual version of the latest stable release is upgraded from the testing repository and every upgraded program is being tested one by one.
After you make an installation once on a virtual machine (such as VirtualBox - more at: Virtualization:Contents), you can take a screenshot of your machine every time you upgrade it to the latest version of the stable repository, so that you can use this image(screenshot) for your upcoming tests. That prevents installing the same packages every time you use a machine upgraded to the latest version of the repository.
The upgraded release is being tested after restarting the system, in order to learn whether the system is capable of doing basic things or not. After this, it is checked with revdep-rebuild command to control if any broken distributed library files in reverse dependencies are missing.
As testing all the characteristics of the programs and the libraries by the Members of Pardus Testing Team isn't possible in terms of knowledge, experience and time; the packages are classified in 3 categories:
- Packages to be tested in details
- Packages to be tested in normal standards and
- Packages to be tested only in installation.
Testing Repository Adresses
- For Pardus 2007 : http://paketler.pardus.org.tr/testci-2007/pisi-index.xml.bz2
- For Pardus 2008 : http://paketler.pardus.org.tr/testci-2008/pisi-index.xml.bz2
- For Pardus 2009 : to be added
Before Reporting Any Bugs
- If you get an installation error, check sha1sum of the image you have downloaded. Burn the CD at DAO mode and at most 16x speed and check if your CD is OK.
- When you get an error, try to understand the error message. Be sure that the reason of the problem isn't your program settings. Do not forget that Google is your best friend.
- Try to repeat the GUI errors by starting the program from console. Attach the error log from the console to your error report.
- Try to repeat the error with the latest stable version of the package. Attach the result to your error report.
See also
- Pardus 2008 Test Team (Turkish language)
