What is Retesting vs Regression Testing?

Retesting (confirmation testing) verifies that a specific fixed defect is actually resolved, while regression testing verifies that the fix, or any change, did not break previously working functionality elsewhere.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

Retesting is narrow and targeted: you take the exact steps from the bug report and confirm the defect is gone on the build that claims to fix it. It uses the same data and steps, and it is always run on the fixed build, never automated away because you need to confirm this particular fix.

Regression testing is broad and preventive: it re-runs a suite of existing tests around the changed area (and often the wider product) to ensure the change introduced no new breakage. Because regression suites are large and run repeatedly, they are the prime candidate for automation, and risk-based selection keeps them from ballooning.

The two usually happen together after a fix: first retest to confirm the bug is dead, then regress to confirm nothing else died with it. Confusing them, for example "automating retesting" or "manually regressing everything every release", is a common sign of shallow process understanding.

WHY IT MATTERS

Why interviewers ask about this.

This is a frequent QA interview distinction. Interviewers want to hear that retesting is targeted and confirms one fix, regression is broad and guards against side effects, and that regression is the one you automate.

EXAMPLE

Example scenario.

A login bug is fixed. QA retests by following the original bug's exact steps to confirm login now works (confirmation testing). Then QA runs the regression suite around auth, session, and the account page to confirm the fix did not break logout, "remember me", or password reset.

TIP

Interview tip.

State the difference in one line (retest = confirm this fix; regression = confirm nothing else broke), then note that regression is what you automate while retesting is targeted and tied to a specific defect.

FAQ

Frequently asked questions.

Is retesting the same as confirmation testing?

Yes. Retesting and confirmation testing are the same thing: re-running the exact steps of a fixed defect on the new build to confirm the bug is actually resolved.

Which one do you automate, retesting or regression?

Regression testing is the prime candidate for automation because it is broad and runs repeatedly. Retesting is targeted to a specific fix, so it is often done manually as part of verifying that defect.