Re-testing is nothing but testing the functionality again and again even after defect is found.
The process of assuring after testing again that the previous bug is fixed is called as ‘Retesting’.
So basically retesting is to test the reported bug by you after developers has made effort in fixing that to make the application work fine.
Retesting is a form of regression testing, where you search through a list of supposedly fixed bugs and then retest the original
steps to make that the test completely passes (as well as the bug being fixed).
Let’s take an example that you found a bug while testing for a website and then you report it to the developers. Now the next thing is for the
developers to fix it. Once the bug that you’ve reported is fixed you need to test the website again if that certain bug is resolved or not.
Retesting is a type of testing performed to check the test cases that were unsuccessful in the final execution are successfully pass after
the defects are repaired
Suppose you were testing some software application and you found bug/defects in some component.
1. You need to test the failed test cases to make sure that the previous failures are gone and application is working fine.
2. Developer will fix that defect and provide you with the new build.
3. You update a bug in bug tracking tool and assign to developer.
Hope this helps
No comments:
Post a Comment