Software Regression Testing Task
Jump to navigation
Jump to search
A Software Regression Testing Task is a software testing task that involves re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change.
- Counter-Example(s):
- See: Change Impact Analysis, Functional Testing, Unit Testing, Software Regression, Software Bug.
References
2020
- (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/regression_testing Retrieved:2020-5-13.
- Regression testing (rarely non-regression testing ) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. If not, that would be called a regression. Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components. [1] As regression test suites tend to grow with each found defect, test automation is frequently involved. Sometimes a change impact analysis is performed to determine an appropriate subset of tests (non-regression analysis ).
- ↑ National Research Council Committee on Aging Avionics in Military Aircraft: Aging Avionics in Military Aircraft. The National Academies Press, 2001, page 2: ″Each technology-refresh cycle requires regression testing.″