Regression Testing
Regression testing verifies that changes to software have not introduced unintended defects into existing functionality.
“A type of change-related testing to detect whether defects have been introduced or uncovered in unchanged areas of the software.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Regression Testing?
Whenever software is modified, regression tests confirm that previously working features continue to operate correctly.
Change validation: Existing functionality is rechecked after modifications.
Risk reduction: Detects unintended side effects.
Automation: Frequently automated because tests are executed repeatedly.
Real World Example
A regulated product team is preparing a release where Regression testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Regression testing as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Regression testing and similar ideas.
The page becomes useful in practice because Regression testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Regression testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Regression testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Regression Testing. Test your understanding with topic-specific questions in our Mock Exams.