Software Regression Testing Task: Difference between revisions

From GM-RKB
Jump to navigation Jump to search
(Created page with "A Software Regression Testing Task is a software testing task that involves re-running functional and non-functional testing|non-functional te...")
 
(ContinuousReplacement)
Tag: continuous replacement
Line 10: Line 10:


=== 2020 ===
=== 2020 ===
* (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/regression_testing Retrieved:2020-5-13.
* (Wikipedia, 2020) https://en.wikipedia.org/wiki/regression_testing Retrieved:2020-5-13.
** '''Regression testing''' (rarely ''non-regression testing''  ) is re-running [[functional testing|functional]] and [[non-functional testing|non-functional tests]] to ensure that previously developed and tested software still performs after a change.  If not, that would be called a ''[[software regression|regression]]''. Changes that may require regression testing include [[software bug|bug]] fixes, software enhancements, [[configuration file|configuration]] changes, and even substitution of [[electronic component]]s. <ref> [[National Academies of Sciences, Engineering, and Medicine|National Research Council]] Committee on Aging Avionics in Military Aircraft: [https://www.nap.edu/catalog/10108/aging-avionics-in-military-aircraft ''Aging Avionics in Military Aircraft'']. The National Academies Press, 2001, page 2: ″Each technology-refresh cycle requires regression testing.″ </ref> 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''  ).
** '''Regression testing''' (rarely ''non-regression testing''  ) is re-running [[functional testing|functional]] and [[non-functional testing|non-functional tests]] to ensure that previously developed and tested software still performs after a change.  If not, that would be called a ''[[software regression|regression]]''. Changes that may require regression testing include [[software bug|bug]] fixes, software enhancements, [[configuration file|configuration]] changes, and even substitution of [[electronic component]]s. <ref> [[National Academies of Sciences, Engineering, and Medicine|National Research Council]] Committee on Aging Avionics in Military Aircraft: [https://www.nap.edu/catalog/10108/aging-avionics-in-military-aircraft ''Aging Avionics in Military Aircraft'']. The National Academies Press, 2001, page 2: ″Each technology-refresh cycle requires regression testing.″ </ref> 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''  ).
<references/>
<references/>

Revision as of 16:22, 2 December 2022

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.



References

2020

  1. 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.″