What is Retesting?

What is Retesting? When to use it? Advantages and Disadvantages

Retesting is testing of a particular bug after it has been fixed. Usually tester raises the bug when they find it while testing the product or its component. This bug is assigned to a developer and he fixes it. Post fixing the bug is assigned to the tester for its verification. This testing is known as retesting.
  • Retesting is done by replicating the same scenario with same data in new build.
  • In retesting those test cases are included which were failed earlier.
  • Retesting ensures that the issue has been fixed and is working as expected.
  • It is a planned testing with proper steps of verification
  • When a bug is raised and is rejected by the developer saying that it’s not re-creatable in their environment then in this case also the testers do the re-testing of the bug to ensure that whether it’s a genuine bug or not.
  • In some cases the entire module is required to be re-tested to ensure the quality of the module.
  • The test cases of retesting cannot be automated.

Example of Retesting

Let’s assume that there is an application which maintains the details of all the students in school. This application has four buttons like Add, Save, Delete and Refresh. All the other buttons functionality are working as expected but on clicking on ‘Save’ button is not saving the details of the student. This is a bug which is caught by the tester and he raised it. This issue is assigned to the developer and he fixes it. Post fixing the issue it’s again assigned to the tester. This time tester tested only the ‘Save’ button functionality. This is called retesting.

When to use Re-testing

  • It is used to verify the specific bug or issue.
  • It is also used to confirm to developers that the issue is valid and re-creatable.
  • It is used to test even the entire module or component in order to confirm the expected functionality.
  • It is used to check the quality of any particular feature or component or module of an application.

Advantages of Re-testing

Below are few of the advantages of re-testing:
  • It confirms that the issue is fixed and working as expected.
  • It improves the quality of the application or product
  • It requires less time for verification because it’s limited to the specific issue or any particular feature.
  • It does not require any new environment setup. Retesting is done with the same data and same environment with new build.

Disadvantages of Re-testing

Below are few of the disadvantages of re-testing:
  • It requires new build for verification of the defect.
  • Once the testing is started then only the test cases of retesting can be obtained and not before that.
  • The test cases for re-testing cannot be automated.
  • It requires additional effort and time because of the re execution of the failed test cases.

Comments

Post a Comment

Popular posts from this blog

What is Dynamic Testing?

What is Dynamic testing technique? This testing technique needs computer for testing. It is done during Validation process. The software is tested by executing it on computer. Example of this  Dynamic Testing Technique :  Unit testing ,  integration testing ,  system testing .
Read more

What is the Software Development Life Cycle (SDLC)?

What are the Software Development Life Cycle (SDLC) phases? There are various software development approaches defined and designed which are used/employed during development process of software, these approaches are also referred as “Software Development Process Models” (e.g.  Waterfall model ,  Incremental model ,  V-model ,  Iterative model ,  RAD model ,  Agile model ,  Spiral model ,  Prototype model  etc.). Each process model follows a particular life cycle in order to ensure success in process of software development. Software life cycle models describe phases of the software cycle and the order in which those phases are executed. Each phase produces deliverables required by the next phase in the life cycle. Requirements are translated into design. Code is produced according to the design which is called development phase. After coding and development the testing verifies the deliverable of the implementation phase against requirements. The testing team follows  Software T
Read more

What is Software Testing Life Cycle (STLC)?

Image
Just like developers follow the  Software Development Life Cycle (SDLC)  likewise testers also follow the  Software Testing Life Cycle  which is called as  STLC . It is the sequence of activities carried out by the  testing team  from the beginning of the project till the end of the project. Software Testing Life Cycle is a testing process which is executed in a  sequence, in order to meet the quality goals. It is not a single activity but it consists of many different activities which are executed to achieve a good quality product. There are different phases in STLC which are given below: Requirement analysis Test Planning Test case development Environment Setup Test Execution Test Cycle Closure Each of the step mentioned above has some Entry Criteria (it is a minimum set of conditions that should be met before starting the software testing) as well as Exit Criteria (it is a minimum set of conditions that should be completed in order to stop the software testing) on the
Read more