Introduction
Stability validation of the corresponding OSGi Framework configuration is achieved by means of continuous runs of the functional test cases (see "Framework validation: functional"). At the end of the stability test, the following conditions should be satisfied:
Test setup
For executing stability validation tests based on the ready projects of test cases for functional validation of the Framework Module (see "Framework validation: functional"), you can use the same project files with slight modifications.
For example, the original com.prosyst.mbs.framework-osgi-7.0.0.prj.xml contains the following section:
<execution>
<mode>consec</mode>
<punit>pass</punit>
<duration>1</duration>
<tunit>min</tunit>
<timeout>100</timeout>
<tcoverloading>1</tcoverloading>
<tcgc>true</tcgc>
. . .
</execution>
For stability testing, increase the duration. If you use the statement <punit>pass</punit>, depending of the times you need the project's test cases to pass, you might increase the duration from 0 to 5 or 50. At the end of the test, the memory state of the framework must be the same as the one after first pass (not as the one before executing any tests because lots of framework modules are lazily initialized).
The <punit> tag specifies the execution punit (progress unit), and namely the units needed to measure the duration defined within the <duration> tag. Possible values are pass, ms, sec, min, hour and day. When the duration time elapses, no more test cases are executed. If there are test cases still running, they are waited to finish. The pass value defines duration of test "passes", i.e. whether you want to execute the project one or several times. The number of repetitions is specified with the <duration> tag.
For more details on test projects and their syntax, refer to the TEE user documentation available in the <osgi_sdk_home_dir>/runtime/osgi/docs/tee directory.