TestEra: a novel framework for automated testing of Java programs
By Darko Marinov, Sarfraz Khurshid. International Conference on Automated Software Engineering, 2001
315 citations recorded by the source corpus.
Subfields: Computational Theory and Mathematics, Software
View Paper: https://www.semanticscholar.org/paper/872be092d35ea82f94343294cc87cb3826db9d84
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computational Theory and Mathematics
- Darko Marinov
- Corina S. Pasareanu
- Sarfraz Khurshid
- Willem Visser
- Koushik Sen
- Suman Sekhar Jana
- Chandrasekhar Boyapati
- Patrice Godefroid
In Software
- Darko Marinov
- Corina S. Pasareanu
- Sarfraz Khurshid
- Koushik Sen
- Willem Visser
- Suman Sekhar Jana
- Chandrasekhar Boyapati
- Angelos Dennis Keromytis
Citations in the corpus
- Korat: automated testing based on Java predicates (2002, methodology): “AA can also be used to check correctness of Java methods by writing method specifications as Alloy models and defining appropriate translations between Alloy instances and Java objects, as demonstrated in the TestEra framework [23].”
- Test input generation with java PathFinder (2004, background): “Somerecent frameworks, most notably TestEra [35] and Korat [10,34], do support non-isomorphic generation of complex structures, such as red-black trees.”
- NEZHA: Efficient Domain-Independent Differential Testing (2017, methodology): “TestEra [49] uses specifications to automatically generate test inputs for Java programs. lava [58] is a domain-specific language designed for specifying grammars that can be used to generate test inputs for testing Java VMs. Unlike N EZHA ’s guided approach, the input generation process of these…”
- Using Frankencerts for Automated Adversarial Testing of Certificate Validation in SSL/TLS Implementations (2014, unknown): “Georgiev et al. carried out a study of certificate validation vulnerabilities caused by the incorrect use of SSL/TLS APIs, as opposed to flaws in the implementations of these APIs [31].”