Risk-Driven Testing

How to find the most important bugs first?

How the concept of Risk can make this happen?

What components to use for assigning Risk?


Whenever there's too much to do and not enough time to do it, we have to prioritize so that at least the most important things get done. In testing, there's never enough time or resources. In addition, the consequences of skipping something important are severe. So prioritization has received a lot of attention. The approach is called Risk Driven Testing, where Risk has very specific meaning.

Take the pieces of your system, whatever you use - modules, functions, section of the requirement Impact is what would happen if this piece somehow malfunctioned. Would it destroy the customer database? Or would it just mean that the column headings in a report didn't quite line up?

Likelihood is an estimate of how probable it is that this piece would fail.