Cargo is a thin wrapper around existing containers (e.g. J2EE containers). It provides different APIs to easily manipulate containers. Cargo provides a Java API to start/stop/configure Java Containers and deploy modules into them. It also offers Ant tasks, Maven 1, Maven 2, Intellij IDEA and Netbeans plugins. There's also a Java API to parse/create/merge J2EE Modules and deployment descriptors.

Using English, write down some stories. Suggest some scenarios to fully illustrate the stories. Split the scenarios into sequences of contexts, events and outcomes. Reuse them to describe and illustrate the different behaviours of your system. Run the stories. If you need some code to make the system behave as it should, write down the behaviour of the code. Run the behaviours. If the code isn't doing what it should, change it so that it behaves. It's like testing, but without the tests.

XHarness is a system test harness for Apache Ant 1.6.x. It allows people to describe their product/system tests in the form of XML as part of an ant build file, describing the tasks and processes that comprise the test cases and what their expected behaviour is. It has powerful process management capabilities, that extend the existing Ant process tasks (exec, java) to allow asynchronous execution of java and native processes (e.g. for client-server tests), synchronization between multiple processes and complex assertions on process and task output (stdout/stderr, file output, coupled with timeouts, etc.). It also has the concept of a "service" that encapsulates the necessary infrastructure for testcases to run (e.g. a Webserver) and adds a number of other useful tasks to the Ant framework, like environment sets and an equivalent to the Unix "which" command. XHarness tests are executed by the Ant framework and the output produced by all tasks and the test results are captured. In that respect, XHarness works similar to the Ant junit task in that it runs testcases and tasks/processes associated with these tests and at the end produces an HTML summary of the tests, listing the result of each testcase as well as the output of the testcase's tasks and processes.

TestDox is an IntelliJ IDEA plugin that provides enhanced navigation and live documentation of JUnit tested code. TestDox has been developed by three comitters. It is about 4 years old and has over 10000 downloads to date according to http://plugins.intellij.net/plugin/?id=96 .

JTestMe dynamically defines smoke test suites for Java applications - dramatically improving the continuous integration cycle time. When running your full test suite (unit, integration, functional, etc), the code is instrumented by JTestMe to record any application Classes which are executed are recorded into a repository. Super-classes and classes that are not directly called by tests are also included so the full scope is captured. When you change any application code, the repository is inspected to determine which tests should be run. These tests can then be run whenever you save a file, as an automatic pre-commit build test suite, or as an automatic smoke test suite for a Continuous Integration tool like CruiseControl. Rather than having to run the whole test suite again, or pre-defined test suites, only the tests that need to be run to exercise the changed code are the ones that are run, dramatically reducing the feedback cycle for most applications. Once the smoke test suite has passed, you would then run the full test suite, in order to fully assure the behaviour of the application (as some changes are beyond the view of the executing code). Maturity: Alpha (currently working, test-driven code) Dependencies: * AspectJ * Java 1.5