What is risk-based testing?

• A. Conducting tests purely on historical data without considering risk.
• B. Prioritizing tests based on assessed risk to the system.
• C. Testing only the most frequently used features.
• D. Testing based on the developer's preference.

Answer: (B)

Risk-based testing focuses testing effort where it matters most by weighing how likely a failure is against how big an impact it would have. This approach ensures the most critical parts of the system get more thorough testing and resources, while less risky areas receive appropriate attention.

That's why prioritizing tests based on assessed risk to the system is the best fit. It means evaluating features or components for their potential to fail and the consequences if they do, such as impact on security, safety, compliance, or business value, and designing and executing tests accordingly.

Other approaches miss that focus. Relying only on historical data ignores current risks and changing priorities. Testing just the most frequently used features looks at usage, not risk, so critical but less-used areas might be neglected. Basing testing on the developer’s preference is arbitrary and not aligned with what could harm the project or organization.