From PardusWiki

This document is created by Semen Cirit in order to explain stable version test processes. For suggestion and contribution:sciritpardus.org.tr

Contents 1 Stable Version Test Process 1.1 Test types for stable version 1.2 Update and new package Tests 1.2.1 Example stable version test e-mail 1.2.2 An example reply to stable version test e-mail 1.3 Security Tests

Stable Version Test Process

Stable version test processes are update and new package tests and security vulnerability tests.

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. For example tester-2009.)

Test types for stable version

• İnstallation Testing
• Functional Testing
• Regression Testing
• Performance Testing
• Security testing

Update and new package Tests

Update and new package tests are for stable version. When a package pass the Ack-Nack phase, it passes to test phase. If any problem found for that package it is taken to stable repository in 7 day.

The Ack packages are listed by test supervisor. After that a new repository created with this package list and stable repository. The link of this repository is:

http://packages.pardus.org.tr/tester-x/pisi-index.xml.bz2 

şeklindedir. The x will be change according to Pardus version. For example for 2009 it will be tester-2009. This repository, the ack package list and related testcases send via test team list to test team members.

These packages are grouped by components, because the testcases for stable version test processes are grouped also by components: http://svn.pardus.org.tr/pardus/2009/stable/ (This link will be changed)

Example stable version test e-mail

Subject:No 20090608 2008 tests


Last day for 2008 stable tests: 15-06-2009 09:00

Desktop component:
-------------------------
qt4-4.4.3-55-18.pisi
qt4-designer-4.4.3-55-18.pisi
qt4-doc-4.4.3-55-16.pisi
qt4-linguist-4.4.3-55-18.pisi
qt4-sql-ibase-4.4.3-55-4.pisi
qt4-sql-mysql-4.4.3-55-18.pisi
qt4-sql-odbc-4.4.3-55-18.pisi
qt4-sql-postgresql-4.4.3-55-18.pisi
qt4-sql-sqlite-4.4.3-55-18.pisi

server component
------------------------
apache-2.2.11-31-9.pisi

programming component:
-----------------------------------
perl-IO-Socket-SSL-1.26-13-4.pisi


The repository: http://packages.pardus.org.tr/testci-2009/pisi-index.xml.bz2

The testcases: http://svn.pardus.org.tr/uludag/trunk/doc/test/2009/testguide/turkish/stable/<comonent-tr>.pdf

All test team members test all packages in the list with assistance of testcases documents under the link http://svn.pardus.org.tr/uludag/trunk/doc/test/2009/testguide/turkish/stable/. For example for apache package test the server-eng.pdf will be used.

The test results grouped and reply to the the e-mail under Ok and Not Ok categories. The failed packages will report to http://bugs.pardus.org.tr/ with assistance of efficient bug reporting document.

An example reply to stable version test e-mail

OK·
---------------------------
qt4-4.4.3-55-18.pisi
qt4-designer-4.4.3-55-18.pisi
qt4-doc-4.4.3-55-16.pisi
qt4-linguist-4.4.3-55-18.pisi
qt4-sql-ibase-4.4.3-55-4.pisi

Not OK
------------------------------
qt4-sql-mysql-4.4.3-55-18.pisi
qt4-sql-odbc-4.4.3-55-18.pisi
qt4-sql-postgresql-4.4.3-55-18.pisi
qt4-sql-sqlite-4.4.3-55-18.pisi
apache-2.2.11-31-9.pisi
perl-IO-Socket-SSL-1.26-13-4.pisi

Security Tests

Security test process starts when the security test team extract a package list. The security updates are merged to stable in 24 or 72 hour according to their criticality.

The other processes are similar with update and new package tests for stable.