






staproject Swiki
Comparative Study of Java Unit Testing Tools
[Primarily Java test generation tools are focused, but the features of helping inspect executions will also be investigated.]
Reports
[Jan 26] Initial Comparison between JPF and JCute on TreeMap
[Jan 26] jCute does not instrument library classes
TODO List
- Install tools (make notes about ease of installation)
- Check wheher these tools can generate tests against bytecode instrumented by InsECT http://www.cc.gatech.edu/~orso/software.html; if so, we can feed to these tools with instrumented bytecode that collects structural coverage on the fly during test generation and execution.
- Double-check these tools against the features of argument generaiton and sequence generation
- Double-check these tools against the output formats of their generated tests
Available tools
Categories
- [Inputs] Analyze only source code:
- [Inputs] Analyze instrumented bytecode: the rest
-
- [Generation] Generate method arguments only: JCrasher, CnC
- [Generation] Generate method sequences only: Rostra, RUTEj, Java Pathfinder
- [Generation] Generate both method arguments and method sequences: Parasoft Jtest, Agitar Agitator, Eclat, jCUTE, eToc, Symstra
- Generation Parameters such as Rostra's iteration number
-
- [Outputs] JUnit Test Classes: JCrasher, CnC, Rostra, Parasoft Jtest, Eclat, eToc, jCUTE
- [Outputs] Textual Test Forms: RUTEj, Java Pathfinder(?), Symstra (JPF implementation?)
- [Outputs] Internal Test Forms: Agitar Agitator(JUnit code generation to be added)
Java Benchmarks
Evaluation Criteria
Publications on comparing tools