Exploratory Testing Risk-Based Exploratory Testing 1 — Questions and Answers
Question 1: What is risk-based testing (RBT) in the context of exploratory testing?
- Prioritizing testing effort toward areas with the highest likelihood and impact of failure (Correct answer)
- Testing only the features classified as 'high risk' by management
- Performing testing without any formal test plan to reduce project risk
- Running all tests in a risk-free sandbox environment
Correct answer: Prioritizing testing effort toward areas with the highest likelihood and impact of failure
Risk-based testing allocates exploratory effort toward areas where defects are most likely to occur and have the greatest impact.
Question 2: Which two dimensions are typically used to assess risk in risk-based testing?
- Likelihood of failure and impact of failure (Correct answer)
- Test coverage and test duration
- Defect density and code complexity
- Team experience and tooling availability
Correct answer: Likelihood of failure and impact of failure
Risk is assessed by combining the probability that something will fail with the severity of the impact if it does.
Question 3: How does a risk register inform exploratory test charter creation?
- It identifies high-priority risk areas that should be translated into targeted charters (Correct answer)
- It replaces the need for charters entirely
- It provides a list of pre-written test cases for each risk
- It assigns bug severity levels before testing begins
Correct answer: It identifies high-priority risk areas that should be translated into targeted charters
A risk register surfaces the areas and scenarios most likely to cause problems, which become the basis for targeted exploratory charters.
Question 4: What is the danger of focusing exclusively on happy-path testing in risk-based exploratory testing?
- High-risk edge cases and error conditions may go untested (Correct answer)
- The happy path will be over-tested, wasting resources
- The application will pass all user acceptance tests
- Performance risks will be automatically mitigated
Correct answer: High-risk edge cases and error conditions may go untested
Happy-path testing misses error handling, boundary conditions, and unusual usage patterns where high-impact defects often hide.
Question 5: In risk-based exploratory testing, what should happen when new risks are identified during a session?
- New charters should be created to address the newly identified risks (Correct answer)
- The session should be extended indefinitely to cover all new risks
- New risks should be ignored until the next formal risk assessment
- The existing charter should be revised retroactively
Correct answer: New charters should be created to address the newly identified risks
Newly discovered risks should trigger new charters, ensuring that exploration follows the evolving risk landscape.
Question 6: Which stakeholder input is most valuable when creating a risk-based test strategy?
- Product owners, developers, and past defect data (Correct answer)
- Only the QA team's historical bug reports
- Automated test coverage reports alone
- Regulatory compliance documents exclusively
Correct answer: Product owners, developers, and past defect data
Combining product owner priorities, developer knowledge of weak spots, and historical defect patterns creates the most accurate risk picture.
Exploratory Testing Risk-Based Exploratory Testing 1
What is risk-based testing (RBT) in the context of exploratory testing?