The DOI matches its Crossref record; 9 of the 9 references it cites were found in a registry or an index.
The ASTOOT approach to testing object-oriented programs
Open accessAbstract
This article describes a new approach to the unit testing of object-oriented programs, a set of tools based on this approach, and two case studies. In this approach, each test case consists of a tuple of sequences of messages, along with tags indicating whether these sequences should put objects of the class under test into equivalent states and/or return objects that are in equivalent states. Tests are executed by sending the sequences to objects of the class under test, then invoking a user-supplied equivalence-checking mechanism. This approach allows for substantial automation of many aspects of testing, including test case generation, test driver generation, test execution, and test checking. Experimental prototypes of tools for test generation and test execution are described. The test generation tool requires the availability of an algebraic specification of the abstract data type being tested, but the test execution tool can be used when no formal specification is available. Using the test execution tools, case studies involving execution of tens of thousands of test cases, with various sequence lengths, parameters, and combinations of operations were performed. The relationships among likelihood of detecting an error and sequence length, range of parameters, and relative frequency of various operations were investigated for priority queue and sorted-list implementations having subtle errors. In each case, long sequences tended to be more likely to detect the error, provided that the range of parameters was sufficiently large and likelihood of detecting an error tended to increase up to a threshold value as the parameter range increased.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
Smalltalk-80: The Language and its Implementation
Goldberg, A., & Robson, D. J. (1983) · HAL · Cited by 3,866
Simple Word Problems in Universal Algebras
Knuth, D. E., & BENDIX, P. B. (1983) · Springer eBooks · doi:10.1007/978-3-642-81955-1_23 · Cited by 1,368
The C++ programming language (2nd ed.)
Stroustrup, B. (1991) · Addison-Wesley Longman Publishing Co., Inc. eBooks · Cited by 859
On testing non-testable programs
Weyuker, E. J. (1982) · The Computer Journal · doi:10.1093/comjnl/25.4.465 · Cited by 606
Abstract data types and the development of data structures
Guttag, J. (1977) · Communications of the ACM · doi:10.1145/359605.359618 · Cited by 461
Specification techniques for data abstractions
Liskov, B., & Zilles, S. (1975) · ACM SIGPLAN Notices · doi:10.1145/390016.808426 · Cited by 364
Software testing based on formal specifications: a theory and a tool
Bernot, G., Claude Gaudel, M., & Marre, B. (1991) · Software Engineering Journal · doi:10.1049/sej.1991.0040 · Cited by 323
Data Abstraction, Implementation, Specification, and Testing
Gannon, J., McMullin, P., & Hamlet, R. (1981) · ACM Transactions on Programming Languages and Systems · doi:10.1145/357139.357140 · Cited by 221
Automatically checking an implementation against its formal specification
Antoy, S., & Hamlet, D. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.825766 · Cited by 109
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
Test input generation with java PathFinder
Visser, W., Pǎsǎreanu, C. S., & Khurshid, S. (2004) · Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis · doi:10.1145/1007512.1007526 · Cited by 501
Harrold, M. J. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336532 · Cited by 360
Using formal specifications to support testing
Hierons, R. M., Bogdanov, K., Bowen, J. P., Cleaveland, R., Derrick, J., Dick, J., Gheorghe, M., Harman, M., Kapoor, K., Krause, P., et al. (2009) · ACM Computing Surveys · doi:10.1145/1459352.1459354 · Cited by 356
Design for testability in object-oriented systems
Binder, R. V. (1994) · Communications of the ACM · doi:10.1145/182987.184077 · Cited by 271
Metadata
- Authors
- Doong, R.-K., & Frankl, P. G.
- Venue
- ACM Transactions on Software Engineering and Methodology
- Published
- 1994-04
- Volume
- 3
- Issue
- 2
- Pages
- 101-130
- ISSN
- 1049-331X (ISSN-L)
- 1557-7392
- OpenAlex
- W2170108788
- Cited by
- 321
- References
- 9
- FWCI
- 30.12
- 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: The ASTOOT approach to testing object-oriented programs. https://app.cochat.ai/papers/10.1145/192218.192221
- The paper
- Doong, R.-K., & Frankl, P. G. (1994). The ASTOOT approach to testing object-oriented programs. ACM Transactions on Software Engineering and Methodology. https://doi.org/10.1145/192218.192221
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.