ISTQB_TEST MANAGEMENT_Risk-Based Testing_1.3.6 Success Metrics and Difficulties Associated with Risk-Based Testing

 

📌 Success Metrics of Risk-Based Testing

Metric Question	Purpose
Were relevant stakeholders involved in risk analysis?	Ensures right people contributed to risk identification
Was stakeholder involvement appropriate?	Confirms quality and relevance of stakeholder input
Were critical production incidents resolved?	Measures how well post-deployment risks were managed
Were most high-priority defects found early?	Validates early risk mitigation via testing
Could the test team explain results in terms of risk?	Shows alignment of test reporting with risk framework
Did skipped tests have lower risk than executed tests?	Confirms correct prioritization during test planning

---

⚠️ Difficulties in Risk-Based Testing

Issue	Cause	Solution
Difficulty in assessing risk	Estimating impact/likelihood is hard	Use historical data and stakeholder assessment
Keen beginnings	Initial enthusiasm fades under pressure	Maintain momentum via regular risk monitoring/reporting
Déjà vu	Same risks repeated = complacency	Involve right people, prioritize only important risks
Key risks missed	Inexperienced/inappropriate participants	Involve trained, experienced stakeholders
Stakeholder churn	Change in stakeholders, emergence of new risks	Treat risk analysis as iterative, not one-time activity

🧠 2. Visual Mind Map for Revision

Mind Map 1: Success Metrics of RBT

Success Metrics
│
├── Stakeholder Involvement
│   ├── Relevant stakeholders involved?
│   └── Was involvement appropriate?
│
├── Production Feedback
│   └── Critical defects escaped & resolved?
│
├── Test Effectiveness
│   ├── High priority defects found early?
│   └── Skipped tests = lower risk?
│
└── Reporting
    └── Risks explained in test results?

---

Mind Map 2: Difficulties & Solutions

Difficulties in RBT
│
├── Risk Assessment Complexity
│   └── Use historical data + stakeholder input
│
├── Keen Beginnings (Short-term pressure)
│   └── Regular monitoring and communication
│
├── Repetitive Risks (Déjà vu)
│   └── Involve right people, focus on relevant risks
│
├── Missed Key Risks
│   └── Train and include experienced participants
│
└── Stakeholder Churn
    └── Treat risk analysis as iterative

---

🎯 3. Scenario-Based Multiple-Choice Questions (MCQs)

✅ Question 1 (K2): Understanding Risk-Based Testing Metrics

Scenario: A test manager reports that all high-priority defects were found during the initial test cycles. Also, skipped test cases had low associated risk.
Which of the following is MOST likely true?

A. Test team followed test automation best practices
B. Risk-based testing approach was successful
C. Stakeholders had no involvement in test planning
D. There was no need for exploratory testing

Correct Answer: B

---

✅ Question 2 (K3): Evaluating a Situation

Scenario: In a financial app release, critical defects escaped into production despite performing risk analysis. Upon review, it was found that only junior testers participated in the risk analysis sessions.
What is the root cause and the BEST solution?

A. Testers weren’t trained – assign more exploratory sessions
B. Too much testing was skipped – test more
C. Key risks were missed – involve appropriate, trained stakeholders
D. Metrics were ignored – track more KPIs

Correct Answer: C

---

✅ Question 3 (K4): Applying Process Improvement

Scenario: The QA lead observes that the same risks appear in every project and testers no longer treat them seriously.
Which action should the test manager take to address this issue?

A. Rotate team members to reduce bias
B. Ignore such risks since they are predictable
C. Involve the right people and prioritize only meaningful risks
D. Reuse the same risk register across all projects

Correct Answer: C

 

Q1: (K2) Which of the following is a valid success metric of risk-based testing?

A. Test design coverage was above 85%
B. Stakeholders could understand test results in terms of risk
C. Test automation reduced execution time
D. All critical test cases were passed

Answer: B

---

Q2: (K3) Risk-based testing was implemented, but many critical defects were found after release. What is MOST likely the cause?

A. Defect priority was incorrectly marked
B. Testers skipped integration testing
C. Inexperienced people did risk analysis
D. Automated tests weren’t used

Answer: C

---

Q3: (K3) The team has been using the same risk list for the last five releases. What issue might arise?

A. Test data may become outdated
B. Developers may lose trust
C. Team may become complacent toward those risks
D. Risk register might become too short

Answer: C

---

Q4: (K4) A test manager wants to avoid stakeholder churn affecting the risk-based testing. What is the BEST approach?

A. Finalize all risks before test execution begins
B. Document risks in the test strategy only
C. Make risk analysis an iterative process
D. Keep test plans generic to accommodate all risks

Answer: C

---

Q5: (K3) A team found that skipped tests had higher risk levels than executed ones. What does this indicate?

A. Good test prioritization
B. Improper risk-based selection of test cases
C. Efficient automation strategy
D. Success in exploratory testing

Answer: B