| Criteria | Regression Testing | Retesting |
|---|---|---|
| Goal | The goal of regression testing is to make sure that the new code changes does not break the existing functionality of the software. | The goal of retesting is to make sure that the reported bug has been fixed after code changes. |
| Scope | Regression testing covers overall software or critical features of the software to check if everything is working as expected. | Retesting covers only the specific failed test case or scenario. |
| When Performed? | Regression testing is performed after a new feature is added to the software or major rework is done. | Retesting is performed after the failed test cases are fixed. |
| Test Cases | Regression testing considers the passed as well as failed test cases to check the overall stability of the software. | Retesting covers only the specific failed test cases/scenarios. |
| Example | Adding new option to sign using Google/Apple does not break the existing login functionality using Email id. Regression Testing will cover checking all the sign-in options to verify that the login works fine. |
User registration fails and an error is thrown after user fills the registration form and clicks on Register button. Once the bug is fixed, Retesting will ensure that the registration process works fine without any error. |
Last active
July 26, 2025 15:10
-
-
Save mfaisalkhatri/dc6e6004b0fe45182653e26e0ff8025a to your computer and use it in GitHub Desktop.
Regression Testing Vs Retesting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment