For understand the Retesting let me give you a example. Suppose in a electric board, one switch is not working. You will call the electrician to fix it. He will fix the switch now you will check to confirm that is this switch working now or not. This is called Retesting or Confirmation Testing.
In terms of Software Testing the process follow like this. Developer write the code for particular module and assign the build to the the QA Team to test. If QA team find any bug in the latest build then QA team assigned that bug to the developer team. Developer Team fix that bug and again develop a new build for testing and assign to the QA team. Now QA team will check and verify that bug assigned to developer team is fixed and this type of testing called Retesting or Confirmation Testing. As per the name suggest retesting means test again to verify.
In Retesting QA team make sure that the Failed Test cases in last run should be pass after the bug fixing process. Priority of Retesting higher then Regression Testing because of that Retesting carried out before the Regression Testing. Defect verification is the part of Retesting. Retesting can't be automate and is planned Testing.
For an example for Retesting in terms of Software testing, Suppose you are as a QA testing the Login Page for any software. You found some bugs. Let say after Login page is not redirecting to the My profile section it is redirecting to Home Page of the Software but as per client requirement page should be redirect to the My Profile Page. You post that bug to the Developer team. They fixes the bug and now you need to again verified that bug that now after Login page should be redirect to the My Profile Page. This is called Retesting.
In terms of Software Testing the process follow like this. Developer write the code for particular module and assign the build to the the QA Team to test. If QA team find any bug in the latest build then QA team assigned that bug to the developer team. Developer Team fix that bug and again develop a new build for testing and assign to the QA team. Now QA team will check and verify that bug assigned to developer team is fixed and this type of testing called Retesting or Confirmation Testing. As per the name suggest retesting means test again to verify.
In Retesting QA team make sure that the Failed Test cases in last run should be pass after the bug fixing process. Priority of Retesting higher then Regression Testing because of that Retesting carried out before the Regression Testing. Defect verification is the part of Retesting. Retesting can't be automate and is planned Testing.
For an example for Retesting in terms of Software testing, Suppose you are as a QA testing the Login Page for any software. You found some bugs. Let say after Login page is not redirecting to the My profile section it is redirecting to Home Page of the Software but as per client requirement page should be redirect to the My Profile Page. You post that bug to the Developer team. They fixes the bug and now you need to again verified that bug that now after Login page should be redirect to the My Profile Page. This is called Retesting.
Comments
Post a Comment