Development Verison Test Process
From PardusWiki
This documentation is created by Semen Cirit in order to explain development version test processes in Pardus. For suggestion and contribution the e-mail:scirit
pardus.org.tr
Development Verion Test Process
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.)
Test types for development version
The test results of development version, can make a far reaching impact to Pardus stable version. The test results can not only fix the bugs but also can give a new feature or can augment the usability of an application.
In alpha and beta versions, the stable repository is not used and all changes and new features automatically reach to user. Therefore all Pardus users partake to ad-hoc testing process. The returns of the users can be taken from http://liste.pardus.org.tr/mailman/listinfo/pardus-kullanicilari and http://bugs.pardus.org.tr/.
Pardus test team members also participate to ad-hoc testing process. But they participate also to functional testing and regression testing processes, in order to test formally and particularly.
Development version tests are very important especially for testing formally and integrally Pardus specific applications with assistance of test guide. The bugs are also reported with assistance of efficient bug report document.
After each development version functional and regression tests are made formally applying testcases by all test team members.
In some cases, the test supervisor can prepare a test version in order to test special applications. These test versions send to testers via an e-mail.
Example e-mail:
A test version is prepared for YALI. Test version: http://cekirdek.pardus.org.tr/~gokmen/Pardus_Minimal_2009.iso Needed testcases document: http://svn.pardus.org.tr/uludag/trunk/doc/test/2009/testguide/english/alphabeta/yali.pdf
