Software Regression Testing Task: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Text replacement - "ions]] " to "ion]]s ") |
||
| Line 23: | Line 23: | ||
=== 2023 === | === 2023 === | ||
* chat | * chat | ||
** A [[Software System Regression Test]] is a [[Testing Process]] that aims to ensure the [[Functionality]] and [[Stability]] of a [[Software System]] after [[ | ** A [[Software System Regression Test]] is a [[Testing Process]] that aims to ensure the [[Functionality]] and [[Stability]] of a [[Software System]] after [[Modification]]s such as [[Bug Fixes]], [[Feature Additions]], or [[Code Refactoring]]. | ||
** Also known as: [[Regression Testing]], [[Software Regression Testing]]. | ** Also known as: [[Regression Testing]], [[Software Regression Testing]]. | ||
** It can identify [[New Defects]] introduced by changes to the [[Code]]. | ** It can identify [[New Defects]] introduced by changes to the [[Code]]. | ||
Latest revision as of 07:31, 22 August 2024
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.
- Context:
- It can be solved by a Regression Testing Process (supported by a regression testing system - possibly built on a regression testing framework).
- It can range from being Automated Software Regression Testing to being Manual Software Regression Testing.
- It can identify New Defects (introduced by changes to the software code).
- It can verify that Previously Working Functionality is still behaving as expected.
- It can help maintain the Reliability and Stability of the Software System.
- It can involve Prioritizing Test Cases based on Criticality and Risk.
- ...
- Example(s):
- Counter-Example(s):
- See: Change Impact Analysis, Functional Testing, Unit Testing, Software Regression, Software Bug.
References
2023
- chat
- A Software System Regression Test is a Testing Process that aims to ensure the Functionality and Stability of a Software System after Modifications such as Bug Fixes, Feature Additions, or Code Refactoring.
- Also known as: Regression Testing, Software Regression Testing.
- It can identify New Defects introduced by changes to the Code.
- It can verify that Previously Working Functionality is still behaving as expected.
- It can help maintain the Reliability and Stability of the Software System.
- It can be performed using Manual or Automated Testing approaches.
- It can involve Prioritizing Test Cases based on Criticality and Risk.
- Associated concepts: Test Case Prioritization, Continuous Integration, Test Automation, Test Coverage Analysis, Manual Testing, Automated Testing.
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.″