Regression testing checks whether a software change has accidentally broken something that used to work. After fixing a tax calculation, for example, a team might retest the corrected calculation and also check that discounts and payments still behave as expected. Those are related checks, but they answer different questions.
What is regression testing?
Regression testing means checking previously tested software after a modification to find unintended effects in functionality that was not meant to change. In plain terms, when developers change one part of an application, they run checks on other important behavior to see whether it still works.
A regression may be a newly introduced defect, or an existing defect that a change has exposed. The key is the purpose of the check: it looks for unwanted consequences of a modification, rather than only verifying the new or corrected behavior.
Regression testing is not limited to one test level. A team may use checks at different levels, depending on the software and the behavior involved. The term describes what the testing is meant to detect, not a particular tool or layer.
#1 Best Overall
Illustrative example: a checkout change
Suppose a team changes how checkout calculates tax. A check that the corrected tax amount is now right tests the fix itself. Regression checks could also cover applying a discount or completing payment, to see whether the tax change affected existing checkout behavior. These examples illustrate the distinction; which checks are appropriate depends on the application and the change.
Regression testing vs. confirmation testing
Confirmation testing—also called retesting—checks whether the original defect has been corrected. Regression testing checks whether the modification has had unintended effects elsewhere. A single change can call for both.
| Check | Question it answers | Example for the tax fix |
|---|---|---|
| Confirmation testing / retesting | Does the previously failing behavior work after the corrective action? | Does the corrected tax calculation return the expected amount? |
| Regression testing | Did the modification cause an unintended problem in previously tested functionality? | Can a customer still apply a discount and complete payment? |
The distinction is about intent, not necessarily separate test tools or separate execution sessions. A team may run the checks together, but should be clear about whether it is confirming the fix, looking for side effects, or doing both. The ISTQB Foundation sample exam, version 1.7 dated February 2, 2022, addresses the difference between regression and confirmation testing.
When is regression testing performed?
Teams perform regression testing after a modification when they need to check for unintended effects. The appropriate timing and breadth depend on the change, the software’s coverage, how often checks are run, the risks involved, and the resources available. There is no universal rule in the cited ISTQB material that every change must trigger the entire test suite.
For a change with a small, well-understood impact, a focused set of checks may provide useful feedback sooner. A broader run may be warranted when important behavior is connected to the change, when coverage needs to extend across more of the system, or when the team judges the risk to justify the extra execution and maintenance effort. These are planning choices, not a fixed formula.
How much regression testing is enough?
Choose checks that exercise important behavior affected by or connected to the change. Then balance the risk of missing a side effect against the time and effort needed to execute and maintain the checks. A useful planning discussion asks:
- Risk and importance: What could go wrong, and how consequential would it be?
- Coverage: Which changed, connected, and otherwise important behavior should be exercised?
- Feedback time: How long will the run take, and when does the team need results?
- Setup and maintenance: Do tests rely on shared data, dependencies, or preconditions that make them costly or fragile?
This is a decision framework, not an official scoring system. The ISTQB Advanced Level Test Automation Engineer syllabus, version 2016, identifies practical factors for planning regression automation, including test frequency, execution time, functional overlap, shared data, dependencies, preconditions, and system-under-test coverage. Those factors can also help a team reason about a focused run versus a broader one.
How to select a useful regression set
- Understand the modification. Identify what changed and what behavior the change is intended to affect.
- Map related behavior. Consider functionality that uses, depends on, or interacts with the changed area, as well as important previously tested behavior that should remain stable.
- Choose checks for meaningful coverage. Prefer tests that exercise distinct, important behavior. Notice when multiple tests overlap substantially, while avoiding the assumption that overlap alone makes a test unnecessary.
- Account for execution conditions. Check whether tests share data, depend on other tests, require particular preconditions, or need setup that affects reliability and runtime.
- Choose the run’s breadth and timing. Weigh the potential impact of a missed defect against execution time and the need for feedback. Use a focused run, a broader run, or both as the situation warrants.
- Review results and adjust. Investigate failures to determine whether they reveal a side effect, a problem in the test or its setup, or another issue. Keep the selected checks aligned with the system and its risks.
When should regression checks be automated?
Automation can make suitable repeated checks faster to execute and can help teams get feedback more often. It is particularly worth considering for checks that run frequently or take time to perform. It does not follow that every check should be automated: automation also has execution, setup, and maintenance costs.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The ISTQB Advanced Level Test Automation Engineer syllabus (version 2016, section 6.2) describes regression testing as an opportunity for automation and notes that today’s functional tests can become tomorrow’s regression tests. It also highlights test frequency, execution time, overlap, shared data, dependencies, preconditions, and system coverage as factors to consider when planning the regression test bed. More frequent feedback can help reduce deployment risk, but automation is a way to support feedback—not proof that a change is safe or that every possible defect has been found.
Visual checks and captured screenshots
For interfaces, teams may also compare captured page images as one kind of visual check. A screenshot can help inspect what a page looked like at capture time, but capturing an image alone does not establish whether it matches an expected result. The team still needs an agreed comparison process and must decide which visual differences matter.
A developer can capture a page directly with a browser or use a screenshot API. For repeatable checks, keep the target URL, viewport, page state, and capture conditions consistent with the expected image; otherwise, differences may reflect changed conditions rather than a software regression. The following API example captures an image, but does not itself perform a comparison or determine whether a test passes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. A single GET request can return a PNG, JPEG, WebP, or PDF. For a visual regression workflow, use the capture as an input to your own comparison and review process; the request below captures a page and saves the response as a WebP file.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBest Value
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for request parameters. Equivalent examples:
Python
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo accepts parameters used by other screenshot APIs, which can make switching easier. It offers full-page capture with lazy images loaded, CSS-selector element capture, dark mode, device presets and custom viewports, retina scale, and PDF options. Other controls include custom CSS and JavaScript, clicking or hiding elements, wait conditions, request and resource blocking, custom headers, cookies and user agent, timezone and geolocation, caching with a chosen TTL, signed links, asynchronous jobs with signed webhooks, bulk capture, a usage API, and an OpenAPI specification.
Before capture, it can accept cookie or consent banners as a visitor and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and whether the request was billed. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. These features do not replace deciding what to test or comparing a capture to an expected result.
The Free plan includes 1,000 shots per month with no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free, and every feature is on every plan. Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchCommon regression-testing problems and fixes
- The fix is checked, but side effects are missed. Add checks for important connected or unchanged behavior; confirming the original defect is not the same as regression testing.
- The suite takes too long for useful feedback. Consider whether a focused run can cover the highest-risk behavior sooner, while planning broader coverage where it is warranted. Review execution time and overlapping tests.
- Automated checks fail inconsistently. Examine shared data, dependencies, and preconditions. The ISTQB syllabus identifies these as planning considerations; a test whose setup is not controlled can make results difficult to interpret.
- Many tests appear to cover the same behavior. Review functional overlap and coverage together. Reduce unnecessary duplication thoughtfully, without removing checks that provide distinct or important coverage.
- A screenshot differs from its baseline. First check whether the URL, viewport, page state, and capture conditions are comparable. A captured image is evidence to review, not by itself a pass/fail judgment.
Further learning
For readers who want a structured foundation, ISTQB describes a Certified Tester scheme built around syllabi, a glossary, sample exams, and a body of testing knowledge. Its Foundation Level is a broad introduction, and its qualifications include specialist areas such as test automation. Certification is not a prerequisite for understanding or planning regression tests.
Frequently Asked Questions
Does regression testing only apply to software releases?
No. It is defined by its purpose—checking for unintended effects after a modification—not by a particular release event.
Can a regression test also be automated?
Yes. Regression testing describes the check’s purpose; automation describes how the check is executed.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
