Difference between Regression and Re-testing are most haunting software testing question asked in an interview by the interviewer and we normally get confused between Regression and Retesting
We as tester do Retesting and Regression testing all our life, Whether we reach on the top of the ladder of this profession or has just started the profession.
Software testing is a kind of fun and if you are not enjoying the software testing, It means you are not following the right method of testing.
Since we people are linked with the testing of software, we all would be pretty familiar with the word Regression and Retesting. Since both sound similar and comes into action just after a bug-fix, so most of the time we people get stuck to the fundamental difference between Retesting and Regression.
Retesting: This is used to test whether defect logged is fixed or not and due to this it is also called as Confirmation Testing
Regression: This is used to see the impact of recently fixed defect(s) or change in the code base.
Here I am going to note down the difference between Retesting and Regression testing
Difference between Regression and Retesting
1-Retesting is done to make sure that bug is fixed and failed functionality is working fine or not, This is kind of verification method followed in the testing field for the fixed bugs. Whereas, Regression is re-execution of the test cases for the unchanged part to see that unchanged functionality is working fine are not.
2- Retesting is planned testing while Regression is known as generic testing.
3- Retesting is only done for failed Test cases while Regression is done for passed test cases.
4- We should always keep this in mind, Re-testing has higher priority than the regression testing. But in bigger projects, Retesting and Regression are done in parallel.But both have its importance in the quality delivery of the product.
Let me explain my things with an example.
For eg: in an application, we need to manage the college accounts department, college hostel department and college academic department. There are three modules. A bug was found in hostel module. So, it needs to be retested once the code is fixed. After this, we would be picking some selected test cases from all module to check any of the ill impacts of a code fix.
Hope you like this post, But if you want to learn how to make test cases then read these two posts
Test Cases for Elevator(Lift)
Important set of test cases for Login Page
Courtesy: Amrit Kaur
One of the best resources to learn Software Testing