Regression testing vs Retesting
Below are the differences between Regression Testing and Retesting.
a) Retesting is carried out to verify defect fix / fixes. Regression testing is done to check if the defect fix / fixes have not impacted other functionality of the application that was working fine before applying the code changes.
b) Retesting is planned based for the defect fixes listed in Build Notes. Regression testing is generic and may not be always specific to any defect fix or code change and can be planned as regional or full regression testing.
c) Retesting involves executing test cases that were failed earlier and regression testing involves executing test cases that were passed earlier build i.e., functionality that was working in earlier builds.
d) Retesting will involve rerunning failed test cases that are associated with defect(s) fixes being verified. Regression testing does not involve verifying defect fix but only executing regression test cases.
e) Retesting always takes higher priority over Regression testing i.e., Regression testing is done after completing Retesting. In some projects where there are ample testing resources, Regression testing is carried out in parallel with regression testing.
f) Though Retesting and regression testing have different objectives and priorities, they equally important for project’s success.
Hi there your community 'NASA' on Google+ is huge now and unfortunately has been swamped by flat earthers and general spam. I'd like to change that and help make the community free of the rubbish and get back to the science. The other moderator Tomasz cannot spare time to moderate and I'm on G+ every day and would love to help, if you could make me a moderator. Please let me know what you think. Many thanks James.
ReplyDelete