Classification Tree Method: Difference between revisions

Revision as of 12:33, 12 August 2013

Revision as of 12:44, 12 August 2013

Line 78:

One way of modelling constraints is using the refinement mechanism in the classification tree method. This, however, does not allow for modelling constraints between classes of different classifications. Lehmann and Wegener introduced Dependency Rules with their incarnation of the CTE.<ref>{{cite journal|last=Lehmann|first=Eckard|coauthors=Wegener, Joachim|title=Test Case Design by Means of the CTE XL|journal=Proceedings of the 8th European International Conference on Software Testing, Analysis & Review (EuroSTAR 2000)|year=2000|url=http://www.systematic-testing.com/documents/eurostar2000.pdf}}</ref> Further features include the automated generation of [[test suite]]s using combinatorial test design (e.g. [[all-pairs testing]]).

=== Prioritized Test Case Prioritization and Test Sequence Generation ===

Recent enhancements to the classification tree method include the [[Risk-based testing|prioritized test case generation]]. Therefore, it is possible to assign weights to the elements of the classification tree in terms of occurrence and error [[Probability|probability]] or risk. These weights are then used during test case generation to prioritize test cases.<ref>{{cite journal|last=Kruse|first=Peter M.|coauthors=Luniak, Magdalena|title=Automated Test Case Generation Using Classification Trees|journal=Software Quality Professional|year=2010|month=12|volume=13|issue=1|pages=4-12}}</ref> Statistical testing is also available.

=== Test Sequence Generation ===

== Advantages ==