On Required Element Testing
- 1 November 1984
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. SE-10 (6) , 795-803
- https://doi.org/10.1109/tse.1984.5010308
Abstract
In this paper we introduce two classes of program testing strategies that consist of specifying a set of required elements for the program and then covering those elements with appropriate test inputs. In general, a required element has a structural and a functional component and is covered by a test case if the test case causes the features specified in the structural component to be executed under the conditions specified in the functional component. Data flow analysis is used to specify the structural component and data flow interactions are used as a basis for developing the functional component. The strategies are illustrated with examples and some experimental evaluations of their effectiveness are presented.Keywords
This publication has 15 references indexed in Scilit:
- On Required Element TestingIEEE Transactions on Software Engineering, 1984
- On Path Cover Problems in Digraphs and Applications to Program TestingIEEE Transactions on Software Engineering, 1979
- Detection of Data Flow Anomaly Through Program InstrumentationIEEE Transactions on Software Engineering, 1979
- On the Automated Generation of Program Test DataIEEE Transactions on Software Engineering, 1976
- Dave—a validation error detection and documentation system for fortran programsSoftware: Practice and Experience, 1976
- Data Flow Analysis in Software ReliabilityACM Computing Surveys, 1976
- Reliability of the Path Analysis Testing StrategyIEEE Transactions on Software Engineering, 1976
- Symbolic execution and program testingCommunications of the ACM, 1976
- An Approach to Program TestingACM Computing Surveys, 1975
- Toward a theory of test data selectionIEEE Transactions on Software Engineering, 1975