The differences between Retesting and Regression testing

-
- Retesting is done to verify defect fix previous in now working correctly where as regression is perform to check if the defect fix have not impacted other functionality that was working fine before doing changes in the code.

- Retesting is specific and is performed on the bug which is fixed where as in regression is not be always specific to any defect fix it is performed when any bug is fixed.

- Retesting concern with executing those test cases that are failed earlier where as regression concern with executing test cases that was passed in earlier builds.

- Retesting has higher priority over regression.

Comments

Post a Comment

Popular posts from this blog

What is Test case

-
A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of Creating test cases can also help find problems in the requirements or design of a Software. Test Case Format Test scenario id test case id test  case Summary Related Requirement Prerequisites Test Procedure Test Data Expected Result Actual Result Status Comment Created By execution Date Tester Test Environment
Read more

The tester should have skill

-
The tester should have skill A destructive Mindset to crack or crash system under test frequently Bring bad news Under worst time pressure  Need to take a different view, a different mindset  How should fault information be communicated 
Read more

Priority vs Severity

-
High Severity – High Priority bug This is when major path through the application is broken, for example, on an eCommerce website, every customers get error message on the booking form and cannot place orders, or the product page throws a Error of page not found. High Severity – Low Priority bug This happens when the bug causes major problems, but it only happens in very rare conditions or situations, for example, customers who use very old browsers cannot continue with their purchase of a product. Because the number of customers with very old browsers is very old version, it is not a high priority to fix the issue. High Priority – Low Severity bug The logo or name of the company is not displayed on the website. It is important to fix the issue as soon as possible, although it may not create cause a System and other component. Low Priority – Low Severity bug The privacy policy page take a long time to load. Not many people view the privacy policy page and slow...
Read more