Software testing techniques (2nd ed.)
Software testing techniques (2nd ed.)
Statistical testing of software based on a usage model
Software—Practice & Experience
The chaining approach for software test data generation
ACM Transactions on Software Engineering and Methodology (TOSEM)
Journal of Systems and Software
Incorporating varying test costs and fault severities into test case prioritization
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
A UML-Based Approach to System Testing
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
The Cow_Suite Approach to Planning and Deriving Test Suites in UML Projects
UML '02 Proceedings of the 5th International Conference on The Unified Modeling Language
Criteria for Generating Specification-Based Tests
ICECCS '99 Proceedings of the 5th International Conference on Engineering of Complex Computer Systems
Successful Test Management: An Integral Approach
Successful Test Management: An Integral Approach
On the economics of requirements-based test case prioritization
EDSER '05 Proceedings of the seventh international workshop on Economics-driven software engineering research
Automatic test case generation for UML activity diagrams
Proceedings of the 2006 international workshop on Automation of software test
Integration testing in software product line engineering: a model-based technique
FASE'07 Proceedings of the 10th international conference on Fundamental approaches to software engineering
Model-based system testing of software product families
CAiSE'05 Proceedings of the 17th international conference on Advanced Information Systems Engineering
| Hi-index | 0.00 |
In practice, available testing budgets limit the number of test cases that can be executed. Thus, a representative subset of all possible test cases must be chosen to guarantee adequate coverage of a test object. In risk-based testing, the probability of a fault and the damage that this fault can cause when leading to a failure is considered for test case prioritization. Existing approaches for risk-based testing provide guidelines for deriving test cases. However, those guidelines lack the level of detail and precision needed for automation. In this contribution, we introduce the risk-based testing technique RiteDAP, which automatically generates system test cases from activity diagrams and prioritizes those test cases based on risk. The results of applying the technique to a practical example are presented and the ability of different prioritization strategies to uncover faults is evaluated.