JCrasher: Selected Testees and Test-Cases

What kind of bugs does JCrasher detect? The following lists several testees on which we ran JCrasher 0.27--with the default search-depth setting of three. The corresponding test-cases are also available.

SPEC Benchmark

We ran JCrasher 0.27 on the Canvas raytracer class--and detected at least one bug. The following contains the JCrasher-generated test-cases.

Programming Homeworks

The following testees are taken from first-year students' programming homeworks. JCrasher detects several robustness problems. Some of them are bugs.
Testee [Author] JUnit Test-Cases [Author]
P1.java [s1] P1Test.java, P1Test1.java [JCrasher 0.27]
P1.java [s1139] P1Test.java, P1Test1.java [JCrasher 0.27]
P1.java [s2120] P1Test.java, P1Test1.java [JCrasher 0.27]
P1.java [s3426] P1Test.java, P1Test1.java [JCrasher 0.27]
P1.java [s8007] P1Test.java, P1Test1.java [JCrasher 0.27]
BSTree.java, BSTNode.java [s2251] BSTreeTest.java, BSTreeTest1.java, BSTreeTest2.java, BSTreeTest3.java, BSTreeTest4.java [JCrasher 0.27]

David Stotts' UB-Stack

The following Java source files are the UB-Stack testee and corrsponding hand-coded test cases by David Stotts, Mark Lindsey, and Angus Antley copied from here. We have made some minor modifications noted below. Tao Xie and David Notkin have referred to these files in their 2003 ASE paper ``Tool-Assisted Unit Test Selection Based on Operational Violations''. Their iterative technique uses the above sets of test cases as initial sets. For each initial set they generate test cases that reveal at least one bug in UB-Stack.

JCrasher 0.27 does not detect any bugs.