Skip to content
← All CTFL glossary terms

Regression testing

Testing performed to detect unintended side effects of a change in unchanged areas of the software.

Syllabus chapters: 2

Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.

Related terms

Regression testing in a practice question

Question 1

During development, before the system's first release, a defect in the discount calculation is fixed. The tester re-runs the test that originally failed, and then runs tests around related pricing features. Which statement is correct?

  1. Both activities are confirmation testing
  2. The first activity is regression testing, the second is confirmation testing
  3. The first activity is confirmation testing, the second is regression testing
  4. Both activities are maintenance testing
Show answer
  • Both activities are confirmation testingOnly the first re-run is confirmation; testing related features is regression testing.
  • The first activity is regression testing, the second is confirmation testingThe roles are reversed: re-running the failing test is confirmation, not regression.
  • Correct answer: The first activity is confirmation testing, the second is regression testingRe-running the originally failing test is confirmation; checking related areas is regression.
  • Both activities are maintenance testingThe system is not yet operational, so this is not maintenance testing; maintenance can otherwise include confirmation and regression testing.

Confirmation testing re-runs the originally failing test to confirm the defect is fixed. Regression testing checks that the change did not introduce unwanted side effects in related or unchanged areas.

Syllabus section 2.2.3

Question 2

In some iterative and incremental development models, each iteration delivers a working prototype or product increment. What does this imply for testing?

  1. In each iteration, both static testing and dynamic testing may be performed at all test levels
  2. Dynamic testing waits for the final increment, when the complete system first becomes executable
  3. Test levels are defined so that the exit criteria of one are part of the entry criteria of the next
  4. Test analysis and design can be omitted, because experience-based techniques need no preparation
Show answer
  • Correct answer: In each iteration, both static testing and dynamic testing may be performed at all test levelsA working increment each iteration allows static and dynamic testing at all levels.
  • Dynamic testing waits for the final increment, when the complete system first becomes executableWaiting for executable code describes sequential models, where code comes in the later phases.
  • Test levels are defined so that the exit criteria of one are part of the entry criteria of the nextExit criteria feeding the next level's entry criteria is how sequential models define test levels.
  • Test analysis and design can be omitted, because experience-based techniques need no preparationExperience-based techniques need no extensive prior analysis, but analysis is not thereby dropped.

Where each iteration delivers a working prototype or product increment, both static testing and dynamic testing may be performed at all test levels within each iteration. Frequent delivery of increments then requires fast feedback and extensive regression testing.

Syllabus section 2.1.1

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.