Skip to content
Related Articles

Related Articles

Software Engineering | Comparison between Regression Testing and Re-Testing

View Discussion
Improve Article
Save Article
  • Last Updated : 15 Sep, 2022
View Discussion
Improve Article
Save Article

Regression Testing: 
Regression Testing is a type of software testing, which is used to verify that modifications in the software or the environment have not caused any unintended adverse side effects. 

Retesting: 
Retesting is done to make sure that the bug is fixed and whether failed functionality is working fine or not, this is a kind of verification method followed in the testing field for the fixed bugs. Most of the testers have confusion with Regression and Retesting. 

Here in this post, we will show the difference between regression testing and retesting. Below is a detailed comparison

S. No.Regression TestingRetesting
1.Regression testing is known as a generic testing.Retesting is known as planned testing.
2.Regression testing is to ensure that changes have not affected the unchanged part of product.Retesting is used to ensure the test cases which failed in last execution are fixed.
3.Regression testing is used for passed test cases.Retesting is used only for failed test cases.
4.Defect verification is not coming under regression testing.Defect verification is coming under retesting.
5.Regression testing can be done either in automation or manual testing.Retesting can not be automated.
6.Regression testing has lower priority than retesting testing but in some cases it can be done in parallel with retesting.Retesting has higher priority than regression testing.
7.Passed test cases can be executed during regression testing.Only failed test cases are re-executed during retesting.
8.During regression testing test cases can be automated.During retesting test cases can’t be automated.
9.It takes more time as it explores the whole application to uncover the bugs.It takes less time as it focusses only on the exploration of a certain defect of the product.
10.Testing for regression is done to look for unanticipated side effects.To ensure the functioning of original problem as expected retesting is carried out. 
11.Regression testing is only performed after a code modification,  in case of implementation of a new feature, or an enhancement. Retesting is performed in the same environment and with the same data but a new build is used.
12.Test cases are obtained from the document specification and bug reports.Test cases are not obtained beforehand but only after the start of testing.  
13.

Pros-

  • Significant role in agile environment in ensuring continuity of business operations.
  • Aids in identification of bugs in the software
  • Constant additions will not hamper the integrity of application
  • Helps in achieving higher CSI (Customer Satisfaction Index)
  • Reduction in unnecessary expenses
  • It can be implemented both ways- manually or automatically.
  • Helps in detection and fixing of bugs

Pros-

  • Verification of the resolved problem and is functioning as intended.
  • Verification time is less because it is only limited to the specific problem or feature.
  • The level of the program’s or product’s is raised.
  • The same data and environment is used to carry out with the new build.
14.

Cons-

  • Stringent timelines
  • Optimization of test cases is difficult
  • Requirement of stable environment
  • Lack of effective communication between different teams also leads to problems
  • Selection of right automated tool is crucial for testing
  • There is slow down in the overall testing as re

Cons-

  • A new build is needed for the purpose of defect verification.
  • No automation of the test cases.
  • Time consuming because of the re-testing of failed test cases.
  • Test cases can only be obtained after the start of testing and not before that.
My Personal Notes arrow_drop_up
Recommended Articles
Page :

Start Your Coding Journey Now!