What is risk-based testing in software development?

• A. Testing exclusively based on stakeholder popularity.
• B. Testing priorities by alphabetical order of modules.
• C. Prioritizing testing efforts on areas with the greatest risk to project objectives.
• D. Testing is performed only after deployment.

Answer: (C)

Risk-based testing focuses on prioritizing testing activities around the areas that pose the greatest risk to achieving project objectives. By evaluating where defects would have the biggest negative impact—such as core business functionality, data integrity, security, performance, or critical integrations—and how likely those defects are to occur, you decide where to concentrate testing effort, how deep to test, and what kinds of tests to run. This approach helps you find problems that would matter most to stakeholders and the project, while using testing resources efficiently. It also often involves early risk assessment and adjusting tests as new information emerges, so high-risk areas get attention earlier in development.

This isn’t about popularity or arbitrary ordering, and it isn’t limited to after deployment. Testing should still cover other areas, but high-risk items receive more focused validation to reduce the chance of critical failures slipping through before release.