ISTQB Experience-Based Testing Techniques 4 — Questions and Answers
Question 1: Which of the following is NOT considered an experience-based testing technique according to ISTQB?
- Error guessing
- Exploratory testing
- Checklist-based testing
- Equivalence partitioning (Correct answer)
Correct answer: Equivalence partitioning
Equivalence partitioning is a specification-based (black-box) technique, not an experience-based one.
Question 2: A tester creates a checklist based on regulatory compliance requirements for a medical device. What type of checklist is this?
- A defect taxonomy checklist
- A domain-specific compliance checklist (Correct answer)
- A random test input checklist
- A code review checklist
Correct answer: A domain-specific compliance checklist
Checklists derived from regulatory or domain requirements target domain-specific compliance risks.
Question 3: Why is exploratory testing especially valuable early in a project when requirements are incomplete?
- It requires complete specifications to function
- It allows testers to learn the system and uncover risks without waiting for full documentation (Correct answer)
- It automatically generates test cases from partial requirements
- It is the only technique that works without a test environment
Correct answer: It allows testers to learn the system and uncover risks without waiting for full documentation
Exploratory testing's flexibility makes it ideal when documentation is sparse, as testers can learn and test simultaneously.
Question 4: In error guessing, a tester suspects that the system mishandles null values. The tester submits a null input to every text field. This approach is an example of:
- Systematic boundary value analysis
- Using a defect taxonomy to guide test design
- Random input testing
- Applying a known defect category to predict failure points (Correct answer)
Correct answer: Applying a known defect category to predict failure points
The tester is applying knowledge that null inputs are a common failure category to predict and find defects.
Question 5: What is the main purpose of a 'debrief' at the end of an exploratory testing session?
- To rewrite the session charter for the next tester
- To review what was tested, what was found, and what remains to be explored (Correct answer)
- To automatically generate regression tests from the session
- To assign defects to developers
Correct answer: To review what was tested, what was found, and what remains to be explored
Debriefs consolidate learning from the session, log findings, and identify gaps for future exploration.
Question 6: A senior tester recommends creating a 'defect taxonomy' to improve error guessing. What is a defect taxonomy?
- A ranked list of all open defects by severity
- A classification of defect types based on past project data and industry experience (Correct answer)
- A tool that automatically categorizes defects in a bug tracker
- A set of test cases targeting only critical defects
Correct answer: A classification of defect types based on past project data and industry experience
A defect taxonomy classifies defect types from experience, helping testers systematically guess where similar defects may appear.
Question 7: Which statement BEST describes how exploratory testing complements scripted testing?
- Exploratory testing replaces scripted testing in agile projects
- Exploratory testing can find defects that scripted tests miss by allowing free investigation beyond defined test cases (Correct answer)
- Scripted testing is only for regression while exploratory is for new features
- They cannot be used together in the same test cycle
Correct answer: Exploratory testing can find defects that scripted tests miss by allowing free investigation beyond defined test cases
Exploratory testing's flexibility allows testers to discover unexpected defects that predefined scripts would not reach.
ISTQB Experience-Based Testing Techniques 4
Which of the following is NOT considered an experience-based testing technique according to ISTQB?