Scribd
Upload
14 views4 pages

10 Retesting RegressioTesting

Regression

Uploaded by

urvashi4301
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
14 views4 pages

10 Retesting RegressioTesting

Regression

Uploaded by

urvashi4301
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

RETESTING VS REGRESSION

TESTING
Retesting
Retesting is a process to check specific test cases that are found with bug/s in the final
execution. Generally, testers find these bugs while testing the software application and assign
it to the developers to fix it. Then the developers fix the bug/s and assign it back to the testers
for verification. This continuous process is called Retesting.

Regression Testing?
Regression Testing is a type of software testing executed to check whether a code change has
not unfavorably disturbed current features & functions of an application.

Difference b/w Retesting and Regression Testing


• Regression testing is performed for passed test cases while Retesting is done only for
failed test cases.
• Regression testing checks for unexpected side-effects while Re-testing makes sure
that the original fault has been corrected.
• Regression Testing doesn’t include defect verification whereas Re-testing includes
defect verification.
• Regression testing is known as generic testing whereas Re-testing is planned testing.
• Regression Testing is possible with the use of automation whereas Re-testing is not
possible with automation.

Example of Regression Testing in Agile Framework:


The below diagram illustrates the role of regression testing in the final delivery of the product
in an Agile framework:

Sprint is a set period of time during which specific work has to be completed and made ready
to be shipped.
In Sprint X, Module 1 is planned to be completed.

During this phase, the developer develops Module 1. The tester performs unit testing on the
module, raises any defects found and retests the fixed defects.

After the issues are fixed and tested, it is deployed to a production-like environment.

In Sprint Y, Module 2 is planned to be completed and both modules are merged.

The development of module 2 is completed and both the modules are integrated. Later,
different types of testing are performed to ensure developed product matches defined
specifications.

• Unit testing- Module 2 is working as desired.


• Integration testing- performed to check data transfer flow between modules.
• Regression testing- performed to check the integration of both modules has not led to
code break.

Finally, the product is deployed to a production-like environment.


In Sprint Z, the final product is delivered.

Development of Module 3 is done, the change requested is incorporated and all three
modules are integrated.

During this phase, various types of testing are performed to guarantee the developed product
works as desired.

• Unit testing- Module 3 is working as expected.


• Integration testing- performed to ensure the transfer of data between all three modules
works fine.
• System testing- checks end to end flows works as expected.
• Acceptance testing- to validate the system is developed as per business requirement.
• Regression testing- performed to check the integration of all modules and
modifications or enhancements in Module 1 has not led to code break.
Finally, the product is deployed to production and is ready to be used by the customers.

Example of Retesting in Agile Framework:

Step 1: Module 1 has been developed to produce output as A+B+2.

Step 2: The module is tested to check if the functionality works as expected. The output
produced is A+B instead of A+B+2. The associated test case failed and a defect is raised.

Step 3: The developer fixes the defect by making necessary changes in code. Then defect is
reassigned to the tester to retest and verify.

Step 4: The defect is retested and output is matched with the expected result. The linked
failed test case is re-run and passed. Finally, the defect is closed.

You might also like