Exploratory Testing Exploratory Testing MCQ 4 — Questions and Answers
Question 1: What is 'pairing' in the context of exploratory testing?
- Running two identical test scripts simultaneously
- Two testers collaborating at one workstation, one driving and one observing (Correct answer)
- Matching test cases to requirements one-to-one
- Using two tools simultaneously for cross-validation
Correct answer: Two testers collaborating at one workstation, one driving and one observing
Paired exploratory testing has one tester operate the software while another observes, asks questions, and takes notes, improving coverage and insight.
Question 2: A tester discovers a bug while exploring Feature A that was actually caused by a change in Feature B. This illustrates which benefit of exploratory testing?
- Systematic regression verification
- Cross-feature interaction discovery (Correct answer)
- Automated dependency mapping
- Boundary value coverage
Correct answer: Cross-feature interaction discovery
Exploratory testing naturally uncovers unexpected interactions between features because testers move freely across the application without rigid scripts.
Question 3: In which SDLC phase is exploratory testing LEAST likely to be the primary testing approach?
- System testing
- Acceptance testing
- Unit testing (Correct answer)
- Beta testing
Correct answer: Unit testing
Unit testing is typically structured and automated at the code level, making exploratory approaches impractical; exploratory testing shines at higher system and acceptance levels.
Question 4: What is the purpose of the 'Saboteur Tour' in exploratory testing?
- Testing the application with deliberately incorrect configurations to see if it fails gracefully (Correct answer)
- Exploring features as a new user unfamiliar with the system
- Testing all happy paths without error injection
- Reviewing security logs for intrusion attempts
Correct answer: Testing the application with deliberately incorrect configurations to see if it fails gracefully
The Saboteur Tour deliberately tries to break the application by supplying wrong data, canceling operations mid-flow, or removing expected resources.
Question 5: Which metric is most useful for evaluating the quality of exploratory testing sessions over time?
- Number of test scripts executed
- Defect detection rate per session hour (Correct answer)
- Lines of code covered by unit tests
- Number of automated tests added
Correct answer: Defect detection rate per session hour
Defect detection rate per session hour helps teams gauge how effectively exploratory sessions are finding meaningful issues relative to time invested.
Question 6: What does 'coverage' mean specifically in the context of exploratory testing?
- The percentage of code lines executed by tests
- The breadth of functionality, risks, and quality dimensions explored by the tester (Correct answer)
- The number of requirements linked to automated test cases
- The ratio of passed tests to total tests
Correct answer: The breadth of functionality, risks, and quality dimensions explored by the tester
In exploratory testing, coverage refers to how broadly the tester has explored features, risks, scenarios, and user types rather than code-line metrics.
Question 7: Which statement about documentation in exploratory testing is most accurate?
- No documentation is produced because exploratory testing is informal
- Lightweight notes, session sheets, and bug reports capture findings without prescribing every step (Correct answer)
- All test steps must be documented before execution begins
- Documentation is only required for regulatory compliance projects
Correct answer: Lightweight notes, session sheets, and bug reports capture findings without prescribing every step
Exploratory testing uses lightweight documentation — session notes, bug reports, and coverage summaries — to record what was learned without over-scripting.
What is 'pairing' in the context of exploratory testing?