The Regression testing and Retesting have its own priorities and its objective but both are most important in the success of the project.
In the testing there are distinctions between many terminologies which are not help to make it better testing. If you search for these terms over web you’ll get different answers for same question, so I think to explore these terms to get exact idea of these testing terms.
When I thinking of this testing then I thinks of reuse of tests those carried out in terms of manual test suite or in automated scripts which help to reduce the risk which may impact on working software, i.e. impact of enhancement or bug fixes are introduces issues or breaking the previous working functionality. Such testing is carried out to make sure that all is in place & not impacting working features.
If we consider the term “Retesting”, regression test has its wide scope of testing & Retesting is a subset of regression testing. If you are testing the specific defect fix then such testing is called as retesting. If you are testing a bug then you wouldn’t say that “I am doing regression of defect”, you should say “I am doing retesting of defect”.
The retesting is to check whether previously failed feature is working in this current fixes or not. This is to be carried out by executing the previously failed test case and verify that previously failed test case is passed. But in this testing we are considering the previously passed test cases, i.e. the functionality was working the previous build.
Retesting means specific defect verification whether mentioned failure case is working as expected or not that sit. But if we think of such testing then we have to consider all passed test cases prior to this build version. The priority to retesting is more regression test because we have to start the regression testing only after completion of the retesting.
Conclusion: To make it simpler here are the definition of regression testing and retesting-
Regression testing: Regression testing is type of testing carried out to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality.
Retesting: Retesting means testing carried out to verify the specific defect mention in the bug.
- Difference between Regression Testing vs Retesting?
- What is a White Box Testing?
- Smoke Testing
- Sanity Testing
- Key to Successful BVT – How to run the Build Verification Test?
- What is Cause and Effect Graph Testing Technique – How to Design Test Cases With Example?
- Positive and Negative Testing In Software Testing
- What is Test data – Tips and Tricks to Create Test Data
- Should We Put Too Much Detail Into Test Cases?
- Measuring Code Quality with Test Coverage Metrics
8 thoughts on “Regression testing is one step ahead than retesting”
Hi, I am working in small software company. I got great great stuff related to regression testing. thanks for sharing
thank you for all the help.
Of course, what a great blog and educative posts, I will bookmark your blog.Best Regards!
very nice explanation…….
Very good information about regression in software testing. Defintley it increases my knowledge about this kind of testing.
Thanks,
-Sweta
Very useful guide on web testing…. pls send the details
sureshid80@rediffmail.com
I am uday loocking for the software testing job in pune plz hepl me to find the job i am fresher (MCM)
i was asked question once in interview ” among two which one is subset of whom ” but i failed to answer
thisblog is quit helpful