JTR / News: Recent posts

This release fixes issues related to the interaction amongst passive and active nodes in a distributed testing session based on the JTR EDiT functionality.

Update is required.

No changes neither at configuration-level nor at the API level have been introduced, and the required libraries have been left unchanged.

Cheers,
Francesco

This minor release fixes a bug introduced with JTR 3.1. The bug was in the jtr.enterprise.ServiceLocator private API, and prevented non-EJB3 SessionBeans from being looked-up.

An upgrade to this minor release is adviced to every JTR-user.

Sorry for the inconvenience,
Francesco

We are on TheServerSide again.

Take a look and discuss @ http://www.theserverside.com/news/thread.tss?thread_id=38500

This new release adds support for testing webservices. A new abstract base runner has been added to the JTR framework (AbstractWsRunner). This is the abstract class every user-defined runner implementation should extend in order to inherit webservices invocation abilities. Finally the jtr.xml configuration file is described by means of an XML schema, so you can validate your own configuration files against the jtr.xsd. The webservices invocation component is pluggable: the JTR framework defines a set of interfaces you can implement if you want to change the default webservices invocation enginge which is based on WSIF and DII (Dynamic Invocation Interface). The definition of which concrete webservice invocation engine to use is located at the top of the jtr.xml configuration file in the factories section.

Follow the link, please:

http://www.theserverside.com/news/thread.tss?thread_id=33856

Francesco Russo
The JTR Project Team

On the 6th of march JTR 2.0 has been released.

As you can read from the release notes the most remarkable update is the brand new support to JMS. You can now write your JMS-based tests as easily as you have always wished.

The JTR 2.0 framework will give you the chance to code only the testing logic. All the boring middleware-related tasks (connecting to ConnectionFactories, opening connections, sharing connections, opening sessions, handleing exceptions, retrieving administered objects, are carried out by the JTR 2.0 runtime on your behalf according to what you have stated in the jtr.xml configuration file.... read more

Finally we are approaching the release of the JTR (Java Test Runner) 2.0.
The new release includes a brand new JMS module that will enable you to easily and rapidily implement your JMS-based tests.

The framework, as you can read from the documentation, enables you to concentrate yourself just on your testing-logic, leveraging on the JTR runtime for all the low-level details such as connecting to your ConnectionFactories, retrieving your administered objects, instantiating both Connections and Sessions and so on.... read more

Finally I've found the time to both prepare and upload the JTR Project home page. It provides you with an helpful mini JTR how-to describing the main concepts and ideas behind the JTR Project, and gives some useful insight into the framework that will surely enable you to use it for your own purposes.

The next step is publishing a complete tutorial, giving major hints about how to develop JTR custom components to be plugged into the JTR runtime.... read more

This is the first release of the JTR (Java Test Runner) framework.
Even though this is a 1.0 rc1 release, I must admit it is really stable. I am currently using it for stress-testing a J2EE application, and I have not faced any problem yet.
So, why an rc1 release? Well, mainly because of I am planning to add some other nice features in the next days (I do hope I am going to find the time I'd need), so I did not feel it was a good choice starting out directly with a 1.0 official release. Furthermore the JTR project is still lacking documentation, and for sure that's the point I am going to work over in the next week-ends.... read more