Code license:	MIT License
Labels:	Java, JUnit, Testing

Show all Featured downloads:
jcrasher-2.1.3.jar

Links:	JCrasher paper (SP&E 2004) Academic homepage JCrasher FindBugs plugin JCrasher and ESC/Java
Feeds:	Project feeds

Project owners:
	csallner

Usage

ant -f jcrasher.xml

It performs all steps completely automatically.

Example

ant -f jcrasher.xml

jcrasher.xml compiles the Java source files under test. It looks for a file like testees.txt and interprets every line as the location of a Java source file under test, relative to the src property in jcrasher.xml. Our testees are trivia/DivByZero.java, trivia/ManyParameters.java, and trivia/NullDeref.java located in the src directory.
jcrasher.xml runs JCrasher on the compiled Java classes under test. JCrasher will generate JUnit test case (as Java source files) for the classes under test. Now we should have the JUnit test cases DivByZeroTest1, DivByZeroTest2, DivByZeroTest3, ManyParametersTest1, etc. Additionally, JCrasher has generated a test suite that aggregates all generated test cases in JUnitAll. (All these files are included in the result zip file generated in step 5.)
jcrasher.xml compiles the generated Java source files (the JUnit test cases).
jcrasher.xml runs JCrasher's extended version of JUnit on the generated test cases. This will enhance the JUnit text output by suppressing redundant warnings.
jcrasher.xml packages the results into a zip file like examples-jcrasher-2.1.3-2007-03-17-2206.zip. This zip file includes the original testee sources, the generated JUnit test case sources, the log output of JCrasher and JUnit, and the configuration files used: jcrasher.xml and testees.txt.

Optionally, you can clean up all generated files (except the zip file) with the following.

ant -f jcrasher.xml clean