ISTQB FOUNDATION 4.0 | Tutorial 37 | Error Guessing | Experience-Based Techniques Techniques | CTFL

Summary

This tutorial delves into experience-based test techniques, emphasizing their reliance on the tester's intuition and past experiences. It highlights the importance of domain knowledge and understanding typical defects in product testing. The video introduces error guessing as a technique, which complements formal methods by targeting areas prone to defects based on tester's experience. Error guessing, or fault attack, is presented as a valuable approach, especially when formal techniques fall short, such as in poorly defined specifications, time pressure, or with teams lacking formal training. The tutorial encourages testers to use their expertise to uncover potential defects, thereby enhancing test coverage and confidence.

Takeaways

• 📘 Experience-based test techniques are driven by the tester's past experience, domain knowledge, and understanding of typical defects found in similar products.
• 🔍 These techniques are informal and rely on the tester's intuition and judgment rather than formal methods or calculations.
• 🚫 Freshers or those without relevant domain experience should not apply experience-based techniques as they lack the necessary background.
• 🛠 Experience-based techniques are secondary approaches and should be used when formal techniques are not applicable.
• 💡 They are particularly useful in scenarios where formal techniques cannot be applied, such as poorly defined specifications, time pressure, or when the testing team lacks formal training.
• 🎯 Error guessing is an experience-based technique where testers use their intuition to identify potential defects based on past experiences and knowledge of common issues.
• 🚀 Error guessing can be conducted as a 'fault attack', a systematic approach where the tester actively seeks out specific types of defects they expect to find.
• 📝 Writing detailed test cases for error guessing is not necessary; high-level outlines or direct interaction with the system can suffice.
• 🤔 Whether a defect is found or not, error guessing provides a win-win situation by either uncovering issues or increasing confidence in the system's functionality.
• 📈 The results of error guessing can be summarized at a high level, evaluating the value added to the overall testing process and the effectiveness of the technique.
• 🌟 The success of experience-based techniques, including error guessing, hinges on the tester's ability to draw from past experiences and apply that knowledge to new testing scenarios.

Q & A

What is the main focus of chapter 4.4 in the tutorial?

Chapter 4.4 focuses on experience-based test techniques, specifically starting with the first technique, error guessing.

What are experience-based test techniques driven by?

Experience-based test techniques are driven by the tester's past experience in testing similar products, domain knowledge, and knowledge of typical defects.

Why are experience-based test techniques not suitable for a fresher or someone switching domains?

Experience-based techniques are not suitable for a fresher or someone switching domains because they require past experience, domain knowledge, and an understanding of typical defects within a specific industry, which they may not possess.

What are the scenarios where experience-based test techniques are the only options to be applied?

Experience-based test techniques are the only options when specifications are poorly defined, there is time pressure, or the testing team is not formally trained on testing fundamentals.

What is the difference between formal and experience-based test techniques in terms of justification and coverage?

Formal techniques are well-documented and defined, making it easier to justify coverage and determine scope. Experience-based techniques are driven by the tester and may not always be justifiable or have clear coverage measures.

Why should experience-based test techniques be seen as a secondary approach?

Experience-based techniques should be secondary because formal techniques are more structured and easier to justify. They should only be used when formal techniques are not applicable.

What is the concept of error guessing in testing?

Error guessing involves the tester using their intuition and past experience to identify potential defects in the system that may not have been caught by formal testing techniques.

What is the term used for the systematic approach of conducting error guessing?

The systematic approach of conducting error guessing is called fault attack.

What is the win-win situation of error guessing in testing?

The win-win situation of error guessing is that if a defect is found, the tester's intuition is validated. If no defect is found, the tester gains increased confidence in the system's functionality.

How can the results of error guessing execution be documented?

The results of error guessing execution can be documented in a high-level summarized way, noting what was done during the execution and how it added value to the overall testing results.

What is the basis for the error guessing technique?

The error guessing technique is based on the tester's intuitions and guesses, informed by past experience with how the application has worked, common developer mistakes, and failures in other applications.