Quality/Test processes

Mer QA process

Mer has two testing processes package and release testing. Check the overall process description.

Package testing

Package testing takes place when a package change is submitted via gerrit. After successful compiling and rebuild of any packages that depend on the package the tests are executed to the package. The test results are then reported back to the gerrit.

Test mapping

One open issue with the package testing is that how to map tests to the package.

If all tests are using test packaging then the mapping could be like

 <package name>:<test package name>[:tr-lite filter]

 bluez:bluez-tests
 bluez:blts-bluetooth-tests:testset=Core

Release testing

(Pre) Release testing has two main test sets: core and feature set.

Core set

The Core set contains set of tests that verify overall quality of the Mer Core release. Test set have tests from all architecture domain and API tests. Core is in that way static that it is executed for every release and test content has only minor changes.

Feature set

Feature set includes tests for those packages that have been changed from the previous release. Basically feature set is set of package testing. The feature set content changes to every release.