Pardus Testing Team
From PardusWiki
(Difference between revisions)
Erkan Yilmaz (Talk | contribs) (just typos + formats (for not interfering in current testing philosophy)) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | This documentation is created by Semen Cirit in order to explain Pardus Linux Distribution Test Team Candidature and Test Processes. For suggestion and contribution please send mail: '''scirit{{at}}pardus.org.tr''' | |
| + | |||
| + | = Pardus Test 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. | 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. | ||
| Line 5: | Line 7: | ||
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. | 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. | 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?= | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | == You need to know a few detail before participating to Pardus Test Team == | |
| − | + | ::* '''For develpment version test processes:''' You have to accept the risk of losing data and systems on your machine. (For every development version test, you can take a backup of your system to an external harddisk.). | |
| − | + | ::* '''For daily usage:''' Testing environment can not be isolated from daily usage. For your individual system you have to use <pre>http://packages.pardus.org.tr/pardus-x-test/pisi-index.xml.bz2</pre> repository. (x means the related Pardus version. For example pardus-2009-test.) | |
| − | * | + | |
| − | + | ||
| − | + | ||
| − | + | ::Thanks to daily usage of test repository, you will be in [http://www.wikihow.com/Make-Adhoc-Testing-More-Effective ad-hoc test process] at any moment. | |
| − | + | ::For evey bug that you find, you have to report it to [http://bugs.pardus.org.tr/ Pardus bug tracking system] with assistance of [[How:Efficient Bug Reporting | efficient bug reporting]] documentation. | |
| − | + | ||
| − | + | ||
| − | + | ::* '''For stable version test processes:''' You can reserve a partition for stable version tests. This system repository will be a repository which is created by test supervisor for stable test process. The tamplate for this repository <pre>http://packages.pardus.org.tr/tester-x/pisi-index.xml.bz2</pre>. (x means Pardus system version. Örneğin tester-2009.) | |
| − | + | ==For participating Pardus Test Team== | |
| − | + | You will be pass the Pardus Test Team Candidature process before being a test team member. After this proocess you will be well aware about Pardus Linux Distribution infrastructure, and can find bugs and also can find a way to resolve bugs. After send an e-mail to '''pardus-test{{at}}pardus.org.tr''', you will be a pardus test team candidate. | |
| − | + | From that moment you will take a [http://svn.pardus.org.tr/uludag/trunk/doc/test/tester-quiz.txt test team member quiz] in order to learn Pardus Linux Distribution infrastructure and bug finding, fixing and reporting. You can consult your mentor if you’re unable to locate answers. For consulting the mail adress is also '''pardus-test{{at}}pardus.org.tr'''. | |
| − | + | After answering these questions properly, you will be a Pardus test team member!!! İndeed the moderator will affirm your test team list membership. | |
| − | = | + | =Pardus Test Süreçleri= |
| − | + | ||
| − | [ | + | ::* [http://en.pardus-wiki.org/Development_Verison_Test_Process Development Version Test Process] |
| − | + | ::* [http://en.pardus-wiki.org/Stable_Version_Test_Process Stable Version Test Process] | |
| − | + | ||
Latest revision as of 13:59, 30 November 2010
This documentation is created by Semen Cirit in order to explain Pardus Linux Distribution Test Team Candidature and Test Processes. For suggestion and contribution please send mail: scirit
pardus.org.tr
Contents |
Pardus Test 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?
You need to know a few detail before participating to Pardus Test Team
- For develpment version test processes: You have to accept the risk of losing data and systems on your machine. (For every development version test, you can take a backup of your system to an external harddisk.).
- For daily usage: Testing environment can not be isolated from daily usage. For your individual system you have to use
http://packages.pardus.org.tr/pardus-x-test/pisi-index.xml.bz2
repository. (x means the related Pardus version. For example pardus-2009-test.)
- For daily usage: Testing environment can not be isolated from daily usage. For your individual system you have to use
- Thanks to daily usage of test repository, you will be in ad-hoc test process at any moment.
- For evey bug that you find, you have to report it to Pardus bug tracking system with assistance of efficient bug reporting documentation.
- For stable version test processes: You can reserve a partition for stable version tests. This system repository will be a repository which is created by test supervisor for stable test process. The tamplate for this repository
http://packages.pardus.org.tr/tester-x/pisi-index.xml.bz2
. (x means Pardus system version. Örneğin tester-2009.)
- For stable version test processes: You can reserve a partition for stable version tests. This system repository will be a repository which is created by test supervisor for stable test process. The tamplate for this repository
For participating Pardus Test Team
You will be pass the Pardus Test Team Candidature process before being a test team member. After this proocess you will be well aware about Pardus Linux Distribution infrastructure, and can find bugs and also can find a way to resolve bugs. After send an e-mail to pardus-testpardus.org.tr, you will be a pardus test team candidate.
From that moment you will take a test team member quiz in order to learn Pardus Linux Distribution infrastructure and bug finding, fixing and reporting. You can consult your mentor if you’re unable to locate answers. For consulting the mail adress is also pardus-testpardus.org.tr.
After answering these questions properly, you will be a Pardus test team member!!! İndeed the moderator will affirm your test team list membership.
