Cited by 426Software Testing and Debugging TechniquesSoftware Engineering ResearchSoftware System Performance and Reliability

JCrasher: an automatic robustness tester for Java

Csallner, Christoph, Smaragdakis, Yannis·2004·Software: Practice and Experience

Abstract

JCrasher is an automatic robustness testing tool for Java code. JCrasher examines the type information of a set of Java classes and constructs code fragments that will create instances of different types to test the behavior of public methods under random data. JCrasher attempts to detect bugs by causing the program under test to ‘crash’, that is, to throw an undeclared runtime exception. Although in general the random testing approach has many limitations, it also has the advantage of being completely automatic: o supervision is required except for off‐line inspection of the test ases that have caused a crash. Compared to other similar commercial and research tools, JCrasher offers several novelties: it transitively analyzes methods, determines the size of each tested method's parameter‐space and selects parameter combinations and therefore test cases at random, taking into account the time allocated for testing; it defines heuristics for determining whether a Java exception should be considered as a program bug or whether the JCrasher supplied inputs have violated the code's preconditions; it includes support for efficiently undoing all the state changes introduced by previous tests; it produces test files for JUnit, a popular Java testing tool; and it can be integrated in the Eclipse IDE. Copyright © 2004 John Wiley & Sons, Ltd.

Integrity signals

Registry

Crossref · 10.1002/spe.602

Cites

22 of 22 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Csallner, C., & Smaragdakis, Y.
Affiliations
Georgia Institute of Technology (US)
Corresponding author
Smaragdakis, Yannis
Venue
Software: Practice and Experience
Publisher
Wiley
Published
2004-06-07
Volume
34
Issue
11
Pages
1025-1050
ISSN
  • 0038-0644 (ISSN-L)
  • 1097-024X
OpenAlex
W2172260321
Cited by
426
References
22
Citations by year
2026: 3 · 2025: 5 · 2024: 8 · 2023: 9 · 2022: 7 · 2021: 10 · 2020: 19 · 2019: 7 · 2018: 28 · 2017: 17 · 2016: 22 · 2015: 25 · 2014: 37 · 2013: 26 · 2012: 24
FWCI
71.41
Type
journal article
Language
en
Open access
closed
Locations
Software Practice and Experience (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
Keywords
robustness testing, Java, random testing, accident detection, parameter space analysis, test case generation, software testing tools

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review