**Notes: Retesting Vs. Regression Testing - Software Testing Tutorial #25** **Understanding Retesting and Regression Testing:** - Regression Testing has been explained in previous tutorials. - Retesting verifies if defects reported earlier have been fixed, focusing on failed test cases. - Both concepts are essential for interviews and practical testing projects. **Retesting Defined:** - Example: Consider an e-commerce website with user registration features. - During testing, two out of ten test cases for Facebook registration fail. - Retesting involves executing only the failed Facebook registration test cases to verify defect fixes. **The Role of Retesting:** - Retesting confirms that specific defects reported earlier have been resolved. - In the example, you'd retest the two initially failed Facebook registration test cases. **Regression Testing: A Deeper Dive:** - Regression Testing verifies changes or fixes in one part of the application don't adversely affect other unrelated parts. - In the example, it ensures that fixing the Facebook registration defects doesn't break the working functionalities of Google, Twitter, or email registration. **The Purpose of Regression Testing:** - Regression Testing covers related modules and test cases affected by changes or defect fixes. - In the example, you might execute a selection of critical test cases for Facebook, Google, Twitter, and email registration, totaling 13 test cases. **Recap:** - **Retesting**: Focuses on re-executing failed test cases after defect fixes. - **Regression Testing**: Includes retesting failed cases and analyzing and executing critical test cases in related modules to ensure that changes haven't adversely impacted the application.
**Notes: Retesting Vs. Regression Testing - Software Testing Tutorial #25**
**Understanding Retesting and Regression Testing:**
- Regression Testing has been explained in previous tutorials.
- Retesting verifies if defects reported earlier have been fixed, focusing on failed test cases.
- Both concepts are essential for interviews and practical testing projects.
**Retesting Defined:**
- Example: Consider an e-commerce website with user registration features.
- During testing, two out of ten test cases for Facebook registration fail.
- Retesting involves executing only the failed Facebook registration test cases to verify defect fixes.
**The Role of Retesting:**
- Retesting confirms that specific defects reported earlier have been resolved.
- In the example, you'd retest the two initially failed Facebook registration test cases.
**Regression Testing: A Deeper Dive:**
- Regression Testing verifies changes or fixes in one part of the application don't adversely affect other unrelated parts.
- In the example, it ensures that fixing the Facebook registration defects doesn't break the working functionalities of Google, Twitter, or email registration.
**The Purpose of Regression Testing:**
- Regression Testing covers related modules and test cases affected by changes or defect fixes.
- In the example, you might execute a selection of critical test cases for Facebook, Google, Twitter, and email registration, totaling 13 test cases.
**Recap:**
- **Retesting**: Focuses on re-executing failed test cases after defect fixes.
- **Regression Testing**: Includes retesting failed cases and analyzing and executing critical test cases in related modules to ensure that changes haven't adversely impacted the application.
Thanks Manoj
I always look forward to your notes
You are making learners job more simple. Thanks manoj
Thank you very much
Thank you 🙏
The way you explained with example is awesome. Thanks a lot
Thank you so much! Keep watching and sharing.
Thank you, Sir. That was really Helpful
nice sir,
beneficial video.
great explanation
Really helps
Thank you sir
Welcome!
Keep watching for more videos.
sir then what is difference between sanity and retesting
Thanks 👍🙏
Welcome 👍 Thank you very much. Keep watching and sharing.