Selecting Software Test Data Using Data Flow Information
IEEE Transactions on Software Engineering
Predicate-based test generation for computer programs
ICSE '93 Proceedings of the 15th international conference on Software Engineering
Constraint Based Criteria: An Approach for Test Case Selection in the Structural Testing
Journal of Electronic Testing: Theory and Applications
Art of Software Testing
Mutation Versus All-uses: An Empirical Evaluation of Cost, Strength and Effectiveness
Software Quality and Productivity: Theory, practice and training
Constraint based structural testing criteria
Journal of Systems and Software
Hi-index | 0.00 |
Several software testing criteria have been proposed during last years with the goal of aiming the test set generation and revealing many faults as possible. They are considered complementary because can reveal different kind of faults and are based on different principles. For example, structural criteria use the internal structure of the program for deriving test cases; Mutation Analysis is a fault-based criterion; and Constraint Based Criteria use constraints to be satisfied during the program execution. Because of this, some questions can be posed, such as: “What criterion should be used or be first applied?”. Many research works compare criteria with the goal of answering these questions. However, some criteria as Mutation Analysis and Constraint Based Criteria are theoretically incomparable and only empirical studies can point out the relation between them. This work presents results from an empirical evaluation of Mutation Analysis and All-Constrained-Potential-Uses criterion considering the factors: cost (number of test cases), efficacy (number of revealed faults) and strength (difficulty of satisfying a criterion, given that another one has been satisfied). The obtained results show an empirical relation, which is used to propose a strategy for application of different testing criteria.