Exploratory Testing Risk-Based Exploration 1 — Questions and Answers
Question 1: What is the primary purpose of risk-based exploratory testing?
- To focus testing effort on areas where defects would have the greatest impact on users or the business (Correct answer)
- To eliminate all risks in the software before release
- To perform exploratory testing only on high-security modules
- To replace formal risk assessments performed by project managers
Correct answer: To focus testing effort on areas where defects would have the greatest impact on users or the business
Risk-based exploration prioritizes testing where failures matter most, ensuring limited testing time delivers maximum risk reduction.
Question 2: What are the two key dimensions of risk commonly used to prioritize exploratory testing?
- Likelihood of failure and impact of failure (Correct answer)
- Number of lines of code and number of developers
- Feature complexity and user interface design quality
- Test automation coverage and manual test case count
Correct answer: Likelihood of failure and impact of failure
Risk prioritization considers both how likely a feature is to fail and how severe the consequences would be if it did, guiding where to focus exploratory sessions.
Question 3: How does knowledge of recent code changes inform risk-based exploratory testing?
- Areas with recent changes are higher risk because new code introduces new defects and may break existing behavior (Correct answer)
- Recent code changes reduce risk because they represent the most thoroughly reviewed code
- Code change history is irrelevant to exploratory testing priorities
- Recent changes should be tested only by the developer who wrote them
Correct answer: Areas with recent changes are higher risk because new code introduces new defects and may break existing behavior
Code change hotspots are proven defect attractors; recent changes, large refactors, and integration of new dependencies all increase the probability of defects.
Question 4: What is a 'risk list' and how is it used in exploratory test planning?
- A prioritized list of potential failure areas used to guide charter creation and session scheduling (Correct answer)
- A compliance document listing all risks that must be signed off before release
- A list of all open bugs ordered by severity in the bug tracking system
- A developer-provided list of known limitations in the current build
Correct answer: A prioritized list of potential failure areas used to guide charter creation and session scheduling
A risk list captures identified product and project risks so testers can create charters targeting the highest-priority areas first.
Question 5: What is 'risk storming' in exploratory testing planning?
- A collaborative workshop where testers, developers, and stakeholders identify risks across all product areas (Correct answer)
- A technique for rapidly generating random test ideas without preparation
- A method for estimating the number of bugs in untested code
- A formal risk assessment process required by ISO standards
Correct answer: A collaborative workshop where testers, developers, and stakeholders identify risks across all product areas
Risk storming is a team activity that combines diverse perspectives to identify product risks more comprehensively than any individual could alone.
Question 6: How should a tester adjust their exploratory approach when testing a safety-critical feature?
- Apply deeper, more thorough exploration with documented session notes and additional negative and boundary testing (Correct answer)
- Test it exactly the same way as non-critical features for consistency
- Leave safety-critical features to automated regression suites only
- Reduce exploratory testing on safety-critical features to avoid accidental production data changes
Correct answer: Apply deeper, more thorough exploration with documented session notes and additional negative and boundary testing
Safety-critical features warrant more intensive exploration, more diverse test conditions, and thorough documentation because the cost of failure is extremely high.
What is the primary purpose of risk-based exploratory testing?