Selecting Software Test Data Using Data Flow Information
IEEE Transactions on Software Engineering
System Testing Aided by Structured Analysis: A Practical Experience
IEEE Transactions on Software Engineering - Special issue on COMPSAC 1982 and 1983
Comparing the Effectiveness of Software Testing Strategies
IEEE Transactions on Software Engineering
An Applicable Family of Data Flow Testing Criteria
IEEE Transactions on Software Engineering
A Formal Evaluation of Data Flow Path Selection Criteria
IEEE Transactions on Software Engineering
Analysis and Refinement of Software Test Data Adequacy Properties
IEEE Transactions on Software Engineering
Test data adequacy measurement
Software Engineering Journal
Art of Software Testing
A Comparison of Some Structural Testing Strategies
IEEE Transactions on Software Engineering
A Formal Analysis of the Fault-Detecting Ability of Testing Methods
IEEE Transactions on Software Engineering
On some reliability estimation problems in random and partition testing
IEEE Transactions on Software Engineering
Clarifying Some Fundamental Concepts in Software Testing
IEEE Transactions on Software Engineering
An Experimental Comparison of the Effectiveness of Branch Testing and Data Flow Testing
IEEE Transactions on Software Engineering
Provable Improvements on Branch Testing
IEEE Transactions on Software Engineering
Software unit test coverage and adequacy
ACM Computing Surveys (CSUR)
The ability of directed tests to predict software quality
Annals of Software Engineering
FAST: a framework for automating statistics-based testing
Software Quality Control
Software requirements validation via task analysis
Journal of Systems and Software
Comparing test sets and criteria in the presence of test hypotheses and fault domains
ACM Transactions on Software Engineering and Methodology (TOSEM)
Test Criteria for Context-Free Grammars
COMPSAC '04 Proceedings of the 28th Annual International Computer Software and Applications Conference - Volume 01
Empirical Software Engineering
A comparison of MC/DC, MUMCUT and several other coverage criteria for logical decisions
Journal of Systems and Software - Special issue: Quality software
Control and data flow structural testing criteria for aspect-oriented programs
Journal of Systems and Software
Software Testing Research: Achievements, Challenges, Dreams
FOSE '07 2007 Future of Software Engineering
Testability transformation: program transformation to improve testability
Formal methods and testing
Is operator-based mutant selection superior to random mutant selection?
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Hi-index | 0.00 |
Software test adequacy criteria are rules to determine whether a software system has been adequately tested. A central question in the study of test adequacy criteria is how they relate to fault detecting ability. In this paper, we identify two idealized software testing scenarios. In the first scenario, which we call prior testing scenario, software testers are provided with an adequacy criterion in addition to the software under test. The knowledge of the adequacy criterion is used to generate test cases. In the second scenario, which we call posterior testing scenario, software testers are not provided with the knowledge of adequacy criterion. The criterion is only used to decide when to stop the generation of test cases. In 1993, Frankl and Weyuker proved that the subsume relation between software test adequacy criteria does not guarantee better fault detecting ability in the prior testing scenario.In this paper, we will investigate the posterior testing scenario and prove that in this scenario the subsume relation does guarantee a better fault detecting ability. Two measures of fault detecting ability will be used, the probability of detecting faults and the expected number of exposed errors.