A Simple and Practical Approach to Unit Testing: The JML and JUnit Way

By Yoonsik Cheon, Gary T. Leavens. European Conference on Object-Oriented Programming, 2002

352 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

The Oracle Problem in Software Testing: A Survey (2015, background): “Araujo et al. provide a systematic evaluation of design by contract on a large industrial system [9] and using JML in particular [8]; Briand et al. showed how to support testing by instrumenting contracts [33] .”
Using Frankencerts for Automated Adversarial Testing of Certificate Validation in SSL/TLS Implementations (2014, background): “Georgiev et al. focus primarily on the incorrect validation of hostnames in server certificates at a different level in the software stack—in applications, transport libraries, and Webservices middleware.”
Korat: automated testing based on Java predicates (2002, methodology): “Cheon and Leavens [6] describe automatic translation of JML speci.cations into test oracles for JUnit [3].”
JCrasher: an automatic robustness tester for Java (2004, methodology): “For instance, Reference [12] proposes a JVM design that allows fast re-initialization without process creation overhead for server applications.”
Symstra: A Framework for Generating Object-Oriented Unit Tests Using Symbolic Execution (2005, methodology): “Typically, checking the correctness (of outputs) for such tests relies on design-by -contract annotations translated into run-time assertions [10, 27] or on model-based te sting [16].”