This is the first release of the Java Test Runner framework (JTR).

JTR-1.0 provides you with the ability to rapidly build test suites for both standard Java applications and for enterprise Java applications. This simply means that you are provided with a set of facilities for handling the basic interaction with your J2EE components. This is accomplished by means of the Service Locator design pattern. Furthermore you can leverage the JTR framework to manage the injection of all the input parameters into your runners (is here that Inversion of Control takes place).

 

The JTR framework even manages for you the lifecycle of your runners during the different epochs and runs of your tests.

Actually what a developer has to do is simply coding one or more runners (according to his/her needs), editing the jtr.xml configuration file that contains the runtime properties that will drive the test and let the JTR framework do its work.

The most important thing to highlight here is that a runner is nothing but a steady Java Bean with two JTR-contract methods.

 

For each non-JTR bean property there must be an accessor & a modifier: this enables the JTR runtime to perform parameters injection at runtime. Maybe it is possible that in the next releases of the JTR framework some kind of bytecode injection or source class enhancement will be applied to add all those accessor & modifier methods to your concrete IRunner implementations.