IEEE Transactions on Software Engineering
The category-partition method for specifying and generating fuctional tests
Communications of the ACM
Approaches to specification-based testing
TAV3 Proceedings of the ACM SIGSOFT '89 third symposium on Software testing, analysis, and verification
A comparison of the decision table and tree
Communications of the ACM
A study of the effectiveness of control and data flow testing strategies
Journal of Systems and Software - Special issue on applying specification, verification, and validation techniques to industrial software systems
Communications of the ACM
Test Case Design Based on Z and the Classification-Tree Method
ICFEM '97 Proceedings of the 1st International Conference on Formal Engineering Methods
A Choice Relation Framework for Supporting Category-Partition Test Case Generation
IEEE Transactions on Software Engineering
Generating, Selecting and Prioritizing Test Cases from Specifications with Tool Support
QSIC '03 Proceedings of the Third International Conference on Quality Software
The Art of Software Testing
Control and data flow structural testing criteria for aspect-oriented programs
Journal of Systems and Software
Using machine learning to refine Category-Partition test specifications and test suites
Information and Software Technology
CHOC'LATE: a framework for specification-based testing
Communications of the ACM
ZB'03 Proceedings of the 3rd international conference on Formal specification and development in Z and B
Software—Practice & Experience
An empirical evaluation of several test-a-few strategies for testing particular conditions
Software—Practice & Experience
IEEE Transactions on Software Engineering
Hi-index | 0.00 |
Two popular specification-based test case generation methods are the choice relation framework and the classification-tree methodology. Both of them come with associated tools and have been used in different applications with success. Since both methods are based on the idea of partition testing, they are similar in many aspects. Because of their similarities, software testers often find it difficult to decide which method to be used in a given testing scenario. This paper aims to provide a solution by first contrasting the strengths and weaknesses of both methods, followed by suggesting practical selection guidelines to cater for different testing scenarios.