Exploratory Testing Exploratory Testing MCQ 5 — Questions and Answers
Question 1: What is 'scenario-based exploratory testing'?
- Testing guided by realistic user stories or usage scenarios rather than low-level scripts (Correct answer)
- Automated playback of recorded user sessions
- Testing individual functions in isolation using scenarios as unit tests
- A method for generating test data from production scenarios
Correct answer: Testing guided by realistic user stories or usage scenarios rather than low-level scripts
Scenario-based exploratory testing uses real-world user journeys as starting points, letting testers investigate how the system handles typical user goals.
Question 2: Which of the following best describes a 'debriefing' anti-pattern in session-based exploratory testing?
- Spending more time debriefing than testing
- Skipping the debrief entirely, leaving session value unmeasured and unshared (Correct answer)
- Requiring testers to read their session notes aloud verbatim
- Holding debriefs only when bugs were found
Correct answer: Skipping the debrief entirely, leaving session value unmeasured and unshared
Skipping debriefs means insights, coverage gaps, and risks identified during sessions are never surfaced to the team, wasting the session's learning value.
Question 3: When a tester uses an application as a hostile user who tries to bypass authentication, this is an example of:
- Load testing
- Security-focused exploratory testing (Correct answer)
- Usability heuristic evaluation
- Boundary value analysis
Correct answer: Security-focused exploratory testing
Security-focused exploratory testing applies an adversarial mindset to probe authentication, authorization, and input validation vulnerabilities.
Question 4: What is the primary advantage of using personas in exploratory testing?
- They eliminate the need for test documentation
- They help testers adopt different user perspectives, broadening coverage of real-world usage patterns (Correct answer)
- They automatically generate test cases from user profiles
- They reduce the time needed for test planning
Correct answer: They help testers adopt different user perspectives, broadening coverage of real-world usage patterns
Personas help testers think and act as specific user types (novice, power user, mobile user), uncovering issues relevant to each segment.
Question 5: A tester systematically enters the maximum allowed length plus one character into every text field. Which heuristic is being applied?
- Equivalence class testing
- Boundary probing (Correct answer)
- Risk-based coverage
- State transition testing
Correct answer: Boundary probing
Boundary probing tests values at and just beyond defined limits, a classic heuristic that frequently exposes off-by-one errors and buffer issues.
Question 6: In exploratory testing, what does 'time boxing' prevent?
- Testers from finding bugs outside their assigned module
- Unlimited scope creep and ensures regular status reporting and reflection (Correct answer)
- Automated tests from running during exploratory sessions
- Testers from writing session notes during testing
Correct answer: Unlimited scope creep and ensures regular status reporting and reflection
Time boxing constrains each session to a fixed duration (typically 60–120 minutes), forcing regular pauses for reflection and preventing aimless exploration.
Question 7: Which of the following scenarios would benefit MOST from exploratory testing over scripted testing?
- Verifying that a calculated tax rate matches a regulatory table exactly
- Investigating how a newly integrated third-party API behaves under unexpected inputs (Correct answer)
- Confirming that a login page accepts a known valid username and password
- Checking that an email notification is sent after order confirmation
Correct answer: Investigating how a newly integrated third-party API behaves under unexpected inputs
Newly integrated or poorly understood components benefit most from exploratory investigation because their behavior under edge cases is unknown and hard to script in advance.
What is 'scenario-based exploratory testing'?