TOOLS '97 Proceedings of the Tools-23: Technology of Object-Oriented Languages and Systems
Program Segmentation for Controlling Test Coverage
ISSRE '97 Proceedings of the Eighth International Symposium on Software Reliability Engineering
Confidence-Based Reliability And Statistical Coverage Estimation
ISSRE '97 Proceedings of the Eighth International Symposium on Software Reliability Engineering
Identification of Categories and Choices in Activity Diagrams
QSIC '05 Proceedings of the Fifth International Conference on Quality Software
An objective comparison of the cost effectiveness of three testing methods
Information and Software Technology
The Effectiveness of T-Way Test Data Generation
SAFECOMP '08 Proceedings of the 27th international conference on Computer Safety, Reliability, and Security
From MC/DC to RC/DC: formalization and analysis of control-flow testing criteria
Formal methods and testing
Testing techniques in software engineering
Testing techniques in software engineering
Practical elimination of external interaction vulnerabilities in web applications
Journal of Web Engineering
Structural test coverage criteria for integration testing of LUSTRE/SCADE programs
FMICS'11 Proceedings of the 16th international conference on Formal methods for industrial critical systems
An intuitive approach to determine test adequacy in safety-critical software
ACM SIGSOFT Software Engineering Notes
Proceedings of the ACM international conference on Object oriented programming systems languages and applications
Heuristic search-based approach for automated test data generation: a survey
International Journal of Bio-Inspired Computation
Comparing multi-point stride coverage and dataflow coverage
Proceedings of the 2013 International Conference on Software Engineering
Hi-index | 0.00 |
There are a number of practical difficulties in performing a path testing strategy for computer programs. One problem is in deciding which paths, out of a possible infinity, to use as test cases. A hierarchy of structural test metrics is suggested to direct the choide and to monitor the coverge of test paths. Another problem is that many of the chosen paths may be infeasible in the sense that no test data can ever execute them. Experience with the use of "allegations" to circumvent this problem and prevent the static generation of many infeasible paths is reported.