Regression Testing:
Regression testing means to re-execute the pass test cases again of older version of build on the modified version of build. to ensure that there is no any side effect of this change on another module or other part of the application.
Testing conducted to ensure application doesn't break post progression testing.
Re-Testing
Re-Testing: After a defect is detected and fixed, the software should be retested to confirm that the original defect has been successfully removed. This is called Confirmation Testing or Re-Testing
Regression testing: Testing your software application when it undergoes a code change to ensure that the new code has not affected other parts of the software.
Re-Testing : The defect logged by tester while testing application and same fixed by developer. In Retesting we check same defect whether fixed or not using steps to reproduce mentioned in the defect.
Regression testing : we check same defect fixes are not impacted other unchanged part of the application, not breaking the functionality working previously and break due to fixing defect.
TEST EXECUTION
Level 0- Sanity, Smoke testing
Level 1- Real time testing
Level 2- Retesting and Regression testing
Level 3-Final testing
Objective of sanity and smoke testing is same as we can proceed for real time testing means all functional and non functional testing(system testing) based on priority. if bug is occured and reported then after modification we have to re execute the fail test cases(retesting, may be pass now) and pass test cases(Regression to ensure no side effect on another part).
No comments:
Post a Comment