Regression testing: Difference between revisions

Revision as of 15:20, 5 November 2023

Revision as of 15:20, 5 November 2023

Line 25:

=== Retest all ===

This technique checks all the test cases on the current program to check its integrity and validate the adverse impact of bug resolving process on another sections. Though it is expensive as it needs to re-run all the cases, it ensures that there are no errors because of the modified code.<ref name=":0">{{Cite conference|date=2008-03-29|title=Understanding Regression Testing Techniques|first1=Gaurav|last1=Duggal|first2=Bharti|last2=Suri|conference=National Conference on Challenges and Opportunities|___location=Mandi Gobindgarh, Punjab, India|citeseerx=10.1.1.460.5875}}</ref>

=== Regression test selection ===

Unlike Retest all, this technique runs a part of the [[test suite]] (owing to the cost of retest all) if the cost of selecting the part of the test suite is less than the Retest all technique.<ref name=":0" />

=== Test casescase prioritization ===

Prioritize the test cases so as to increase a test suite's rate of fault detection. Test case prioritization techniques schedule test cases so that the test cases that are higher in priority are executed before the test cases that have a lower priority.<ref name=":0" />