Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,13 +1,15 @@
---
id: regression-testing
title: "Regression Testing: What It Is & How to Automate It"
title: "Regression Testing"
sidebar_label: Regression Testing
description: "Learn what regression testing is, the different types (full, partial, risk-based), and how to automate it with tools like Keploy for faster releases."
description: "How to automate regression testing with Keploy: capture and replay tests and mocks from real traffic, run them in CI on every change, and track code coverage."
tags:
- explanation
- Glossary
keywords:
- API
- automated regression testing
- regression testing with keploy
- keploy
head:
- tag: link
attrs:
Expand All @@ -21,6 +23,8 @@ head:

Regression testing can be performed manually or using automated tools. Manual regression testing involves re-running a subset of test cases that have been previously executed to ensure that they still pass. Automated regression testing uses software to execute test cases automatically, which can save time and resources.

For a full guide, including types, techniques and examples, see our [complete regression testing guide](https://keploy.io/blog/community/regression-testing-an-introductory-guide). To generate regression tests from real API traffic, see Keploy's [regression testing tool](https://keploy.io/regression-testing).

## Different Types of regression testing:

**Full regression testing**: This involves re-running all of the test cases in a test suite. This is the most comprehensive approach, but it can be time-consuming and resource-intensive.
Expand Down
Loading