PIT is a fast mutation testing system for Java that makes it possible to test the effectiveness of your unit tests.
You can think of mutation testing as either as an automated test of your tests, or as a much more in depth form of code coverage.
PIT runs your tests against automatically modified versions of your application code. When the application code changes, it should cause a test to fail. If a test does not fail it may indicate an weakness in the suite.
See http://pitest.org for further details.
With the JUnit analysis feature, you can send test run data to an analysis server. The server computes useful results to help you gauge your tests over time: Which atomic tests are likeliest to fail? Has the performance of your test suite had sudden improvements or regressions?
Source: https://github.com/khellste/junit
Details and a tutorial available at above link. Open to any comments or suggestions.
New - Version 3.0.1.RELEASE has been released. This mini-release fixes bug PDM-43 (http://www.jemos.eu/jira/browse/PDM-43)
PODAM is a Java tool to auto-fill POJOs / JavaBeans with data.
The full documentation can be found on PODAM home page
The source code is available at GitHub
the Maven dependencies can be found at Maven Central
With this junit core extension, you can specify the methods to be run in a collection of full qualified method names. Take a look at the following example to get an idea on how this works:
public class RunSome {
public static void main(String[] args) throws SecurityException,
ClassNotFoundException, NoSuchMethodException {
MethodRunnerJUnitCore methodRunner = new MethodRunnerJUnitCore();
String[] methods = new String[] { "ch.rethab.TestClass.someMethod",
"ch.rethab.AnotherClass.anotherMethod" };
methodRunner.runMethods(Arrays.asList(methods));
}
}
Find more information on my blog: http://docode.rethab.ch/2011/02/28/custom-junit-method-runner/
With dp4j.jar as a library of your project you can DIRECTLY ACCESS private methods in your tests. Reflection API code will be injected directly into the AST (i.e during compilation). For example, the following will work: }
public class JunitTest11{
OpenPojo is a library that enables testing and enforcing POJO's behavior, as well as runtime identity management through deep introspection.
OpenPojo uses reflection to create meta-representation for POJO classes that can then be run through the extensible & configurable validation framework. Validation helps enforce structure of code (i.e. public fields, naming convention, etc), or behavior expectations (i.e. set/get only sets and gets without altering value).
Jtoc is a library for writing test assertions in Java, which provides an easy way to write contracts with java's inner class. Compared with other libraries, Jtoc focuses on completely test the contracts without changing the original design of the class. It supports Unit testing, where the written JUnit tests could be used in the test-project Jtoc generated without any change.
Jtoc is created by using two open source library -- javaparser created and maintained by J. V. Gesser as the Java grammar parser, apache-commons-logging as the logger.
Mistletoe is a JUnit extension intended for integration testing. In technical terms, it is a JUnit test suite runner presenting the test results via HTTP as a Web page.
Accessive is a tool that allows you to access private field or methods for testing purposes. That means that you don't have to make some of your methods or field package protected just to allow for testing.
Accessive uses reflection and dynamic proxies to access private portion of your objects, allowing you to keep them strongly encapsulated and still be able to test their internals.
For more details visit http://code.google.com/p/accessive/.
Jailer is a tool for database subsetting and sampling. It allows you to simply export test data for DbUnit based unit tests from production databases.
For more information visit http://jailer.sourceforge.net/
Features