Asynchronous Testing Framework
Add the support for asynchronous testing to existing unit testing frameworks.
Jamiba is a Java micro-benchmarking suite, designed for measuring the low-level performance of applications written in Java.
A Portable Thin Client & Server Pair for XA / 2PC Testing
A portable testing tool to validate the configuration of XA and two-phase commit for Java EE 6 Containers. The tool permits the stress-testing, performance characterization and correct transaction semantics of distributed transactions across Three XA resource managers by Exception Injection. The thin-client can be run from the command-line or inside the IDE. The server side component includes EJB packaging and some simple Web servlet support for retrieving diagnostic and performance data from the testbed.
An "Alternative IO" layer.
The alio library can be dynamically pre-linked to existing executables and replaces file IO (i.e. calls to glibc's IO functions). This allows to gather statistics about IO, create IO trace files, or even implement a different IO behaviour (e.g. use separate IO servers to handle IO).
A library for monitoring the garbage collection of app objects
gcRadar is not a static code anayser but it is a library using which is ment to beused in your source code and it will monitor and report the lifetime events of yuor objects. gcRadar can provide this information by using callbacks, log4j & polling. gcRadar can monitor entities ranging from individula objects to full object trees comprising of is-a & has-a relationships. By using gcRadar you can monitor the lifetime of the objects that are created by your application in runtime, gcRadar enables the application to be aware of the memory constaraints that arise at runtime. The workings of the mythical Java Garbage Collector have for long eluded the common developer. Now by gcRadar enable you to record the life and death of objects at runtime.
A fluent language to write perftences
Performance test engine written in Java and exposed as a fluent API for writing JUnit tests. Perftence can also be used without JUnit by using perftence-api distribution package. Full test results are provided in html, which can published directly with different CI's (e.g. Jenkins/Hudson). Runtime test statistics are also provided through logging (e.g. using slf4j-log4j and log4j). Pertence tool can also be used for finding out threading issues. Just write a test that uses the component you need to test for threading issues and assign load of threads to the test. Thanks to my employer (Nokia) for letting me publish the initial version of this tool as open-source!