ISTQB FOUNDATION 4.0 | Tutorial 20 | Retesting | Confirmation Testing | Regression Testing | CTFL

Summary

This tutorial delves into the ISTQB Foundation level certification, focusing on Chapter 2.2.3 about confirmation and regression testing. It explains that these tests are conducted as part of change-related testing, ensuring that defects are fixed and that no new issues arise from changes. Confirmation testing, often called retesting, verifies a defect fix, while regression testing checks for unintended consequences. The tutorial highlights the importance of impact analysis and the suitability of these tests for automation.

Takeaways

• 📚 The tutorial is focused on the ISTQB Foundation Level certification, specifically discussing testing throughout the SDLC in Chapter 2.
• 🔍 The segment 2.2.3 of the tutorial is about confirmation testing and regression testing, which are categorized as change-related testing due to their conduction upon application changes.
• 🔑 Confirmation testing, often known as retesting, is conducted to verify that a reported defect has been fixed. It's the first step after a developer returns the fixed code to the tester.
• 🌐 ISTQB uses the term 'confirmation testing' instead of 'retesting' to emphasize the purpose of testing, which is to confirm the resolution of a defect, not just repeating a test.
• 🛠️ Confirmation testing may involve rerunning previously failed test cases or adding new ones to cover changes made during the defect fix, adhering to the principle of the 'Pesticide Paradox'.
• ⏱️ In resource-constrained situations, confirmation testing could be limited to the steps that should reproduce the defect and verify its resolution.
• 🔄 Regression testing ensures that the original functionality of the application remains intact after changes have been made, such as fixing a defect.
• 💊 The analogy of visiting a doctor for regression testing is used to illustrate the importance of checking for any adverse side effects caused by changes or fixes in the application.
• 🔍 Regression testing is not limited to defect fixes but is also applicable during updates, upgrades, and migrations, emphasizing its broad scope in change-related testing.
• 🤖 Regression testing is a strong candidate for automation due to its repetitive nature and is often included in continuous integration (CI) pipelines in DevOps practices.
• 📈 Impact analysis is crucial for optimizing regression testing efforts by identifying which parts of the software could be affected by changes, thus reducing unnecessary testing.

Q & A

What is the main focus of Chapter 2 in the ISTQB Foundation Level certification tutorial?

The main focus of Chapter 2 is on testing throughout the SDLC, specifically discussing test levels and types, with a detailed look at confirmation testing and regression testing as part of change-related testing.

Why are confirmation testing and regression testing considered as change-related testing?

Confirmation testing and regression testing are considered change-related because they are conducted in response to changes made in an application, such as fixing a defect or making updates.

What is the primary purpose of confirmation testing?

The primary purpose of confirmation testing is to verify that a reported defect has been successfully fixed and is functioning as expected after the developer's modifications.

What is the difference between confirmation testing and retesting according to the ISTQB?

While many organizations use the term 'retesting' to refer to repeating a test, the ISTQB uses 'confirmation testing' to emphasize that the test is being repeated with a specific objective: to confirm the resolution of a reported defect.

What is the 'Pesticide Paradox' mentioned in the script?

The 'Pesticide Paradox' refers to the principle that fixing a defect may necessitate adding new test cases to improve the overall quality and test coverage, rather than just rerunning the failed test cases.

What are the different approaches to conducting confirmation testing?

Confirmation testing can involve executing all test cases that previously failed due to the defect, adding new test cases to cover any necessary changes made during the fix, or, when resources are limited, simply rerunning the steps that should reproduce the failure and checking that it no longer occurs.

What is the primary goal of regression testing?

The primary goal of regression testing is to ensure that all parts of the system that were working correctly before a change are still functioning properly after the change has been made.

Why is regression testing a strong candidate for automation?

Regression testing is a strong candidate for automation because it is often repeated to ensure that new code changes do not introduce issues, and automating these tests can save time and effort in the long run.

What is the role of impact analysis in the context of regression testing?

Impact analysis helps to identify which parts of the software could be affected by a change, allowing testers to optimize the extent of regression testing and focus on areas that are most likely to be impacted.

Can confirmation testing and regression testing be applied at all levels of testing?

Yes, confirmation testing and regression testing can be applied at all levels of testing, including static and dynamic testing, whenever a defect is fixed or a change is made.

What is the significance of conducting both confirmation and regression testing after a defect is fixed?

The significance lies in ensuring that not only is the original defect resolved, but also that no new issues or side effects have been introduced in other parts of the system as a result of the fix.