Framework validation: functional

Guidelines for the functional validation of the Framework module.

Test cases

Test cases provided for the Framework Module are located in the testcases directory of the OSGi Runtime Validator.

Project files

The following TEE project files are available in the tee/sa/projects directory of the OSGi Runtime Validator or of the osgi part of the target image are related to the functional validation of the Framework module:

• com.prosyst.mbs.framework.demos-bo.prj.xml – Executes basic bundle operations: install, start, stop, update, uninstall, of the functional and demo bundles of the Framework Module.
• com.prosyst.mbs.framework-osgi.prj.xml – Executes functional tests written by the OSGi Alliance for the framework.

  If you want to use this test project make sure that you have retrieved all OSGi Alliance test cases described in the TEE project file and copied them to the testcases directory.

• com.prosyst.mbs.framework-prj.xml – Executes functional tests for the framework.

Start scripts

To setup the environment for running the test cases via tee there are:

• tee.bat
• tee.ini
• tee.sh

Call the server command with tee option to activate the settings these files provide.

To start the TEE on the target image, execute the following instructions:

1. Copy the relevant bin/vms/<vm_name> directory to the osgi folder of the target image.
2. Open a command prompt to the bin/vms/<vm_name> directory and type the following command:

   server tee

Additional details to the general procedure for validation

This section provides additional directions for executing functional validation over the OSGi framework.

1. Copy the testcases directory from the OSGi Runtime Validator (located in the runtime-validator directory) to the home directory of OSGi Runtime (default is osgi).
2. In a console window execute the server tee security command in the bin/vms/<vm_name> OSGi Runtime directory.

When validating the framework state it is required that all services for validated bundles also be validated. To specify a set of optional services, or skip service validation altogether a new attribute for the bundle tag: match.service.count was introduced. If set to true, the validator will check if the number of services registered by the bundle is the same as the number of services described in the validation XML. If set to true, and there are no services described for the bundle, the validation will pass only if the bundle does not register any services. Default value is false.