Achieving software quality with testing coverage measures
- 1 September 1994
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in Computer
- Vol. 27 (9) , 60-69
- https://doi.org/10.1109/2.312032
Abstract
Coverage testing helps the tester create a thorough set of tests and gives a measure of test completeness. The concepts of coverage testing are well-described in the literature. However, there are few tools that actually implement these concepts for standard programming languages, and their realistic use on large-scale projects is rare. In this article, we describe the uses of a dataflow coverage-testing tool for C programs-called ATAC for Automatic Test Analysis for C/sup 3/-in measuring, controlling,and understanding the testing process. We present case studies of two real-world software projects using ATAC. The first study involves 12 program versions developed by a university/industry fault-tolerant software project for a critical automatic-flight-control system. The second study involves a Bellcore project of 33 program modules. These studies indicate that coverage analysis of programs during testing not only gives a clear measure of testing quality but also reveals important aspects of software structure. Understanding the structure of a program, as revealed in coverage testing, can be a significant component in confident assessment of overall software quality.Keywords
This publication has 8 references indexed in Scilit:
- A data flow coverage testing tool for CPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2003
- Coverage measurement experience during function testPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- A coverage analysis tool for the effectiveness of software testingPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Improving the N-version programming process through the evolution of a design paradigmIEEE Transactions on Reliability, 1993
- Applying reliability models more effectively (software)IEEE Software, 1992
- Assuring Design Diversity in N-Version Software: A Design Paradigm for N-Version ProgrammingPublished by Springer Nature ,1992
- An applicable family of data flow testing criteriaIEEE Transactions on Software Engineering, 1988
- Selecting Software Test Data Using Data Flow InformationIEEE Transactions on Software Engineering, 1985