Japex Lifecycle

External documentation

See the Japex manual on how the lifecycle is supposed to work.

Japex settings that have an impact on how the tests run

Number of threads

Japex can run tests in multiple threads. To do this, it creates multiple instances of a driver class to execute. (Details)

Warmups

Japex can "warm up" your tests before it actually runs the benchmarking code. The whole framework is written using the assumption that each Driver class is stateless. Unfortunately, we need a place to start the Mule server so that your performance tests can actually do something with it. (Details)

Runs

Japex can instantiate more than one object per driver class. (Details)

Mule Lifecycle

There are a number of use cases for Mule with Japex:

• Mule is started/stopped for the entire TestSuite
• Mule is started/stopped for a single driver class
• Mule is started/stopped for each TestCase

In order to implement the use cases above, a custom MuleDriver class comes with the framework on which you can specify which Mule lifecycle you want.