Deployment readiness depends on understanding the risk of releasing the software. The metrics provided include execution, design, defect counts, and coverage but do not quantifyresidual risk, which reflects remaining risks post-testing.
Evaluation of Options:
A. Number of tests passed:
Incorrect. While important, it doesn't directly provide insight into the remaining risk.
B. Number of defects outstanding:
Incorrect. Though critical, it’s only one aspect of assessing readiness and doesn’t provide the full picture of residual risk.
C. Residual risk:
Correct. Residual risk quantifies untested areas and unresolved issues, vital for decision-making.
D. Planned vs actual cost of testing:
Incorrect. While useful for process evaluation, it’s not directly tied to deployment readiness.
Syllabus Alignment:
The syllabus emphasizes risk-based approaches, highlighting residual risk as a critical deployment readiness metric (TM-1.3.4).
[References:, ISTQB Advanced Level Test Management Syllabus (TM-1.3.4), ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit