Regression Testing
<< Return to Testing Techniques
Regression Testing for Web Sites – Basic Guide
What is Regression Testing?
Regression testing means re-testing existing features to make sure that recent changes (new features, bug fixes, config updates) did not break anything that worked before. It is usually done before release, or after code changes.
How to Prepare?
Use a predefined test suite – a list of important test cases that cover core features. These should include both functional and critical user flows (e.g. login, checkout, search). Make sure the test environment is stable and close to production.
How to Execute?
Follow each test case step-by-step. Compare the actual results to expected results. If you find any issue, log a defect clearly with all needed details (steps to reproduce, screenshots, expected vs actual). Mark each test as Passed, Failed, or Blocked. Focus on accuracy and repeatability.
When to Run Regression Tests?
- After each new build or deployment
- After fixing bugs
- Before major releases
- Regularly in continuous integration (CI) pipelines
Examples:
- A payment form worked before but now shows an error after a recent update — this should be caught by regression.
- A search function gives incorrect results after a backend change — another common regression issue.