Difference between Sanity and Re-testing
Most of you have asked the difference between Sanity testing and Re-testing.
Here is an answer for it.
Sanity Testing:
Sanity Testing refers to the testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs/errors have been fixed and no further issues are introduced due to these changes. The process of Sanity Testing is as follows –
A software build is received first.
Determine that the proposed functionality works roughly as expected after changes.
If the sanity test fails, the build is rejected.
If the sanity test passes, it is passed for further testing.
Re-testing:
Re-Testing refers to the testing again of a module to ensure that the bug is fixed. This means it confirms the test cases that failed in the final execution are passing after the errors/defects are fixed. The process of Re-Testing is as follows –
At first an error is detected in any module of the application.
Then it undergoes correction/modification by the developer.
After the developer has solved and tested the issue again, it is called Re-Testing.
Hope this helps you.
Don't forget to follow @software_testing_hacks
.
.
#sanitytesting #retesting #manualtesting #softwaretesting