Java Test Runner 3.1
has been released. JTR is an IoC-based Java testing framework aimed at building stress-test suites both for JSE-based projects and for back-end JEE components (JEE session beans, JMS resources, WebServices).
This minor release features a set of improvements that extend the usability and improve the overall experience of the developer, introducing support for EJB 3 session beans, too.
With JTR, developers can only focus on writing their test cases, while the JTR runtime takes care of scheduling runners, resolving, instantiating and injecting all those resources required by the testing logic.
The most relevant updates:
- Support to EJB 3 session beans lookup and instantiation
- More IRunner concrete implementations are allowed to use at runtime the same JMS-configuration even if one of the configured JMS-connections is declared as not shareable: the JTR runtime takes care of associating a uniquely generated client-id with the current JMS-connection in use.
- Your IRunner concrete implementations are no longer required to provide public setter methods for those properties that should be injected according to the configuration provided in the jtr.xml file: only private properties can suffice.
- Another version of the ServiceLocator.getEJBObject(...) method has been added. This new version changes the last accepted parameter from Hashtable to EnterpriseConfig, and should be used in place of the former one for newly developed runners.
Message was edited by: email@example.com