The DOI matches its Crossref record; 7 of the 7 references it cites were found in a registry or an index.
Selecting Software Test Data Using Data Flow Information
Abstract
This paper defines a family of program test data selection criteria derived from data flow analysis techniques similar to those used in compiler optimization. It is argued that currently used path selection criteria, which examine only the control flow of a program, are inadequate quate. Our procedure associates with each point in a program at which a variable is defined, those points at which the value is used. Several test data selection criteria, differing in the type and number of these associations, are defined and compared.
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
Flow Analysis of Computer Programs
Hecht, M. S. (1977) · Cited by 724
On testing non-testable programs
Weyuker, E. J. (1982) · The Computer Journal · doi:10.1093/comjnl/25.4.465 · Cited by 606
Self-citationCurrent trends in programming methodology
Yeh, R. T., & Chandy, K. M. (1977) · CERN Document Server (European Organization for Nuclear Research) · Cited by 545
Theories of Program Testing and the Application of Revealing Subdomains
Weyuker, E. J., & Ostrand, T. J. (1980) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1980.234485 · Cited by 223
Self-citationMethodology for the Generation of Program Test Data
Howden, W. E. (1975) · IEEE Transactions on Computers · doi:10.1109/t-c.1975.224259 · Cited by 196
SELECT---a formal system for testing and debugging programs by symbolic execution
Boyer, R. S., Elspas, B., & Levitt, K. N. (1975) · Proceedings of the international conference on Reliable software - · doi:10.1145/800027.808445 · Cited by 166
The applicability of program schema results to programs
Weyuker, E. J. (1979) · International Journal of Parallel Programming · doi:10.1007/bf00995175 · Cited by 61
Self-citation
Cited by
Software unit test coverage and adequacy
Zhu, H., Hall, P. A. V., & May, J. H. R. (1997) · ACM Computing Surveys · doi:10.1145/267580.267590 · Cited by 1,247
A methodology for controlling the size of a test suite
Harrold, M. J., Gupta, R., & Soffa, M. L. (1993) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/152388.152391 · Cited by 657
Using Mutation Analysis for Assessing and Comparing Testing Coverage Criteria
Andrews, J. H., Briand, L. C., Labiche, Y., & Namin, A. S. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.83 · Cited by 481
Failures and fixes: a study of software system incident response
Sillito, J., & Kutomi, E. (2020) · 2020 IEEE International Conference on Software Maintenance and Evolution (ICSME) · doi:10.1109/icsme46990.2020.00027 · Cited by 14
Metadata
- Authors
- Rapps, S., & Weyuker, E. J.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 1985-04
- Volume
- SE-11
- Issue
- 4
- Pages
- 367-375
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W1985551847
- Cited by
- 1,075
- References
- 7
- FWCI
- 26.90
- Type
- journal article
- Language
- en
- Open access
- closed
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: Selecting Software Test Data Using Data Flow Information. https://app.cochat.ai/papers/10.1109/tse.1985.232226
- The paper
- Rapps, S., & Weyuker, E. J. (1985). Selecting Software Test Data Using Data Flow Information. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.1985.232226
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.