Retesting vs Regression Testing : When We Do Retesting(With Example)

In this tutorial We are going to learn about the What is the main difference between two retesting and regression and we will learn the basic difference between Retesting vs Regression Testing.

Contents

What is Retesting?
Benefits of retesting
Retesting vs Regression
Live API Testing Project that You can Add in your Resume – PART 2
Live API Testing Project that You can Add in your Resume – PART 1
DevOps Concepts That Every QA Should Know 1
How I Got Rejected by 27+ Companies
What is Mobile Testing? | Types of Mobile Testing | Mobile Testing Tutorial 1
5 Real Time Live Projects Web Automation Projects for Manual Testers

What is Retesting?

In the retesting in software testing, It basically means testing a bug that has been fixed.Most of the Time Tester finds a bug in the Application(Web or mobile).

It logs it in the JIRA and Assign it to Dev, after dev fixes it, Dev assign back to Tester to verification.Now Tester verify the bug, This is known the Retesting.

Benefits of retesting

1. Test the cases that are failed only
2. Fast execution.
3. Only have to perform the important or failed cases

Retesting vs Regression

Retesting	Regression Testing
To confirm the test cases that failed in the final execution are passing after the defects are fixed.	To confirm whether a recent program or code change has not adversely affected existing features.
Retest are not automated.	Regression can be automated.
Only bug fixes related test-cases are checked.	Nearly all the testcases are checked in Regression.
Only fixed testcases are runned.	New code changes should not have any side effects to existing functionalities