This article is a stub. You can help starLiGHT.Engine by expanding it.

The information provided in this article are not finally implemented in this way. It is a proposal which should be used.

Contents 1 Test Management Policy 1.1 Regression test policy 1.2 Feature test policy 1.3 Unit test policy

Test Management Policy

There are usually three different test scenarios used during development and release management of the starLiGHT.Engine:

• The regression test
• The feature test
• The automated unit tests

Before the release of a new version of the starLiGHT.Engine different tests will be executed by the QA-Team and by executing the unit tests. Only if this tests succeed a new version will be released.

Regression test policy

n/a

Feature test policy

n/a

Unit test policy

At the moment the coverage of the Unit tests is very poor. We have 242 Unit-Tests with a coverage of only 4%. Most of starLiGHT.Collections and the Initializers of the Particle-System are covered by the unit tests.

The unit tests are executed before a new release candidate will be released. Only if all tests are succesful a release should be made.

For every bug that is filed in mantis, a unit test has to be created. This unit test have to trigger the bug and must be cleared before closing the bug. This avoids that similar bugs are introduced in future versions.

Language:	English