The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
A methodology for controlling the size of a test suite
Open accessAbstract
This paper presents a technique to select a representative set of test cases from a test suite that provides the same coverage as the entire test suite. This selection is performed by identifying, and then eliminating, the redundant and obsolete test cases in the test suite. The representative set replaces the original test suite and thus, potentially produces a smaller test suite. The representative set can also be used to identify those test cases that should be rerun to test the program after it has been changed. Our technique is independent of the testing methodology and only requires an association between a testing requirement and the test cases that satisfy the requirement. We illustrate the technique using the data flow testing methodology. The reduction that is possible with our technique is illustrated by experimental results.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
(1979) · Cited by 43,841
Compilers: Principles, Techniques, and Tools
Aho, A. V., Sethi, R., & Ullman, J. D. (1986) · Cited by 8,082
Selecting Software Test Data Using Data Flow Information
Rapps, S., & Weyuker, E. J. (1985) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1985.232226 · Cited by 1,075
Software testing techniques (2nd ed.)
Beizer, B. (1990) · Cited by 744
An approach to software fault localization and revalidation based on incremental data flow analysis
Taha, A.-B., Thebaut, S. M., & Liu, S.-S. (2003) · IEEE Annual International Computer Software and Applications Conference (COMPSAC) · doi:10.1109/cmpsac.1989.65142 · Cited by 73
Cited by
The oracle problem in software testing: A survey
Barr, E. T., Harman, M., McMinn, P., Shahbaz, M., & Yoo, S. (2015) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2014.2372785 · Cited by 1,104
TestTube: a system for selective regression testing
Chen, Y.-F. R., Rosenblum, D. S., & Vo, K.-P. (1994) · doi:10.5555/257734.257769 · Cited by 262
GZoltar: an eclipse plug-in for testing and debugging
Campos, J., Riboira, A., Perez, A., & Abreu, R. (2012) · Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/2351676.2351752 · Cited by 208
Metadata
- Authors
- Harrold, M. J., Gupta, R., & Soffa, M. L.
- Venue
- ACM Transactions on Software Engineering and Methodology
- Published
- 1993-07
- Volume
- 2
- Issue
- 3
- Pages
- 270-285
- ISSN
- 1049-331X (ISSN-L)
- 1557-7392
- OpenAlex
- W1998393968
- Cited by
- 657
- References
- 5
- FWCI
- 12.64
- Type
- journal article
- Language
- en
- Open access
- bronze
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: A methodology for controlling the size of a test suite. https://app.cochat.ai/papers/10.1145/152388.152391
- The paper
- Harrold, M. J., Gupta, R., & Soffa, M. L. (1993). A methodology for controlling the size of a test suite. ACM Transactions on Software Engineering and Methodology. https://doi.org/10.1145/152388.152391
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.
