Skip to content
This repository has been archived by the owner on Jul 10, 2024. It is now read-only.

Testing

Philipp Haussleiter edited this page Nov 25, 2015 · 1 revision

Testing

Obviously, unit tests can be done using JUnit and will be run automatically, when building the project with Maven.

But to actually test the bundles working with each other and exposing their respective services, integration testing is a necessity.

For now we are going to use Pax Drone 0.2.1 (to be renamed to Pax Exam). Pax Drone allows us to write tests that can be run in a number of different OSGi frameworks, starting with a fresh configuration each time.

The Pax Drone based integration tests are located in the IntegrationTest module. There is another module called TestBundle that contains a very simple bundle that is being deployed and called by the integration tests.

Unfortunately, Pax Drone doesn’t seem to be capable of deploying framework extensions to Equinox and Deployment_to_Equinox for, well, launching. In other words, our weaving does not work with Pax Drone.
To do some basic testing there is another test bundle called Pulsar. It simply calls a method on the TestBundle periodically. When launched with the config.ini from the plugins folder (as can be done with buildAndRun.xml), these calls will use BundleBee and may be remote calls.

Clone this wiki locally