Regression testing
Also called: Regression
Re-running tests to check that new changes didn't break things that used to work.
Definition
Regression testing re-tests existing features after code changes, bug fixes or updates to make sure nothing that worked before is now broken. Because it is repeated often, it is a common candidate for automation.
In practice
After the team adds Google Pay to checkout, you re-run the card payment and PayPal tests to make sure those still work.
Learn it in context
Lessons that use this term.
- How QA Hiring WorksCareer
- What Is Software Testing?Fundamentals
- How to Write a Bug ReportTutorials
- SDLC and STLCFundamentals
- Levels of TestingFundamentals
- Types of TestingFundamentals
- Estimating Testing EffortTutorials
- User Stories and Acceptance CriteriaTutorials
- Exploratory TestingTutorials
- Your First 90 Days as a TesterCareer
Related terms
- RetestingRunning the same test again to confirm that a reported bug is really fixed.
- Smoke testingA quick check of the most important features to decide if a build is stable enough to test further.
- Sanity testingA quick, focused check that a specific fix or change works and nothing obvious around it broke.
- Test suiteA group of related test cases that are run together.