Regression testing
Checking whether changes to software have broken functionality that used to work
Regression testing (rarely, non-regression testing) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change. If not, that would be called a regression.
Nº Q917415 ★★
Uncommon · Knowledge
Regression testing
Checking whether changes to software have broken functionality that used to work
Regression testing (rarely, non-regression testing) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change. If not, that would be called a regression.
Last price
—
Floor price
—
7-day median
—
30-day sales
0
30-day range
—
In circulation
0
Price history
median
low – high
sales
No sales in this period
Show table
| Date | median | Low | High | sales |
|---|
Sales history
- Last sale
- —
- 30-day average
- —
- 30-day low
- —
- 30-day high
- —
- Sales 7d
- 0
- Sales 30d
- 0
No sales yet.
Anonymous sales: no buyer or seller shown. Figures count player-to-player sales only.
From Wikipedia
Regression testing (rarely, non-regression testing) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected 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 (hardware). 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).
Text: Wikipédia, CC BY-SA 4.0. · Image: Ezgi2015 (CC BY-SA 4.0) ·
Related cards
Software testing
Investigation conducted to provide information about the quality of a software product or service under test and enable the business to understand the risks of software implementation
Nº Q188522 ★★★
Black box
System where only the inputs and outputs can be viewed, and not its implementation
Nº Q29256 ★★★
Debugging
Process of finding and resolving defects or problems within a computer program
Nº Q845566 ★★
Unit testing
Software testing method by which individual units of source code are validated
Nº Q907375 ★★
Smoke testing (software)
Preliminary software testing to reveal simple failures to aid assessment of whether main functions of the software appear to work correctly
Nº Q17143088 ★★
A/B testing
User experience research methodology, consisting of a randomized experiment with at least two variants, denoted as A and B
Nº Q1810071 ★★★