Retesting in Software Testing

When you execute a test case more thanonce in case of verifying whether a particular functionality is working fine or not, you call it as “Retesting”.

You raise a defect and assign it to a developer. Developer fix it and give you a fix in the next release or in a few days depending on the process being followed in your company. Now, what will you do?

How will you ensure that the fix built by the developer is working fine?

You will need to re-execute your failed test caseand verify if the functionality has been corrected or not.

So, when you re-test that particular functionality again and update your observations is called “Retesting in Software Testing”.

You as a tester can say Retest failed if it not working well after the fix,

OR

you can say Retest Blocked if something is blocking you to retest that functionality,

OR

you can say Retest verified and closed. Here, are the brief 3 stages:

Retest Failed

Retest Blocked

Retest verified and closed

A defect will then be closed. Basically, the cycle rotates between a tester and a developer.

This is about “Retesting in Software Testing”. Please feel free to add more to it. I hope this will be helpful to you.