Exploratory Testing Knowledge 3 — Questions and Answers
Question 1: Which concept best describes using known error-prone areas of a codebase to guide exploratory testing?
- Equivalence partitioning
- Risk-based test focus (Correct answer)
- Boundary value analysis
- Statement coverage
Correct answer: Risk-based test focus
Risk-based focus directs exploratory effort toward areas most likely to contain defects, such as recently changed or historically buggy modules.
Question 2: What is the 'test oracle problem' in exploratory testing?
- Difficulty accessing the database to verify stored values
- The challenge of determining whether an observed result is correct without a definitive reference (Correct answer)
- Inability to automate the tests that were explored manually
- Lack of a test environment that matches production
Correct answer: The challenge of determining whether an observed result is correct without a definitive reference
Without a clear oracle, the tester must rely on domain knowledge, heuristics, and judgment to decide if behavior is acceptable.
Question 3: Which heuristic model uses the acronym 'SFDIPOT' to guide exploratory testing?
- The Boundary Value Model
- The San Francisco Depot Model (James Bach's heuristic) (Correct answer)
- The State Transition Heuristic
- The Defect Density Index
Correct answer: The San Francisco Depot Model (James Bach's heuristic)
SFDIPOT (Structure, Function, Data, Interfaces, Platform, Operations, Time) is a product element heuristic by James Bach to ensure broad coverage.
Question 4: In exploratory testing, what is 'pairing'?
- Linking a test case to its corresponding requirement
- Two testers working together simultaneously—one drives, one observes and takes notes (Correct answer)
- Assigning each bug to a paired developer
- Running the same scenario on two different OS versions
Correct answer: Two testers working together simultaneously—one drives, one observes and takes notes
Pairing (pair testing) combines two perspectives in real time, catching more issues and building shared knowledge.
Question 5: What does 'time-boxing' provide in an exploratory testing session?
- A way to measure the lines of code tested per hour
- A fixed duration that creates focus and makes sessions reportable and manageable (Correct answer)
- An automated timer that pauses the application under test
- A legal constraint on how long a tester can work
Correct answer: A fixed duration that creates focus and makes sessions reportable and manageable
Time-boxing (e.g., 90-minute sessions) keeps exploration focused, prevents rabbit holes, and makes effort visible to managers.
Question 6: Which source of knowledge is LEAST useful for designing exploratory tests on a brand-new, undocumented feature?
- User interviews and personas
- Analogous products and industry standards
- Previous version test scripts for an unrelated module (Correct answer)
- Bug history from similar features in the codebase
Correct answer: Previous version test scripts for an unrelated module
Test scripts for an unrelated module offer no relevant insight; domain analogy, user research, and bug history from similar features are all more informative.
Question 7: What distinguishes 'freestyle' exploratory testing from 'scenario-based' exploratory testing?
- Freestyle uses automation; scenario-based is always manual
- Freestyle has no guiding charter; scenario-based explores within a real-world user scenario (Correct answer)
- Freestyle is performed by developers; scenario-based by QA only
- Freestyle requires two testers; scenario-based requires one
Correct answer: Freestyle has no guiding charter; scenario-based explores within a real-world user scenario
Freestyle exploration is open-ended and charter-free, while scenario-based exploration anchors the session in a realistic user journey.
Which concept best describes using known error-prone areas of a codebase to guide exploratory testing?