CISC 327 Lecture Notes - Lecture 18: Regression Testing
25 Nov 2017
School
Department
Course
Professor
Document Summary
Regression testing * see slides, he"s going fast: regression a return to a former or less developed state. Purpose: ensure that existing functionality is not broken with new versions, ensure that intended changes do what they"re supposed to, catch accidental or unintentional changes, reduces costs. Methods: establishing a regression test set, maintaining a regression test set, observable artifacts. Incrementally compare the results of tests for each new version of the software only to the previous version. Adding retiring tests: add and validate new tests with updates, retire failure tests after a fixed # of new versions do not exhibit this, operational tests must be maintained and retired/replaced. Include at least the direct outputs of the software, but also other indicators of behavior. Advantages: previous functionality never accidentally lost, previous fixed bugs never reappear in product, virtually all accidental bugs are caught before deployment, virtually no unintentional changes in the behavior slip into production, users observe very high level of quality.
