The JTR Project is a Java distributed testing framework conceived to fill a gap existing today most notably in the open-source world that’s the lack of a single tool that could help in developing from simple to complex test suites in Java with particular emphasis on the stack of backend-technologies embraced by the JEE specification.

The JTR Framework

The JTR Framework is aimed at fastening the development of both functional and stress-test suites for verifying the requirements and robustness of both JSE and JEE projects. The JTR Framework supports you in writing components meant for testing:

1. •standard JSE components / applications

2. •EJBs conforming to both J2EE 2.x and JEE specifications

3. •MOM-based JSE and JEE systems (JMS)

4. •web-services (both document-based and rpc-like)

The JTR Framework has been written following the principles of IoC (Inversion of Control). Following this approach it lets developers focus exclusively on the test-logic, bereaving him/her of the burden to think about dealing with a great number of issues generally related with resource retrieval, multithreading management, tests parameterizations, error handling and so on. The JTR Framework lets you concentrate solely on the testing logic, leveraging on the JTR Runtime to deal with other important tasks on your behalf.

The JTR Runtime

The JTR Runtime provides you with the following features:

•  multiple runner instances management (runners-multithreading and scheduling)
• runner instances parameterization
• scripted parameters initialization (only with JTR 5)
• built-in statistical functions for parameters initialization (only with JTR 5)
• transparently run JUnit 4 test-cases (only with JTR 5)
• management of JMS resources
• stub-less (or dynamic) webservices invocation
• automatic error handling
• test results collection and inspection via the JTRConsole
• effortless distributed testing

JTR Customization

The JTR Project is an highly customizable product. This feature enables you to mold it in the way that better satisfy your needs and requirements. Customizing JTR is an easy process that requires you to become confident with those pluggability point exposed by the JTR Framework. Further information are provided in a dedicated section of the

Adherence to standards

JTR leverages on a large number of both industry and de-facto standards under the hood (JMS, J2EE, JEE, JAX-WS, JAXB, RMI, Log4J) and is integrable in every development environment by means of Ant.

JTR Test

A JTR Test is a test-suite defined by:

1. a number of epochs

2. a set of customizable JTR-components called Runners

3. an optional set of cooperating JTR-nodes

4. a set of JTR-runners

5. an optional set of enterprise configurations

6. an optional set of JMS configurations

7. an optional set of Web-Services bindings

8. an optional set of library-scripts and parameterization-scripts

Epochs

An epoch defines a discrete fraction of time in the time-window required by the whole test-suite. During an epoch each runner will execute all of its duties for a configurable number of times, thus subsequent epochs are used to repeat for the desired number of times the same sequences of tests.

JTR-Components

This advanced configuration concept is covered in a later section.

JTR-Nodes.

This advanced configuration concept is covered in a later section.

JTR-Runners

The JTR-runner is the most important user-defined software component (probably the only one) you will work with. A JTR-runner represents a specific testing-logic.