Risk-based Testing – An effective measure to deal with Risks in Software Testing

Risk-based Testing – An effective measure to deal with Risks in Software Testing

Before explaining Risk based testing, it is necessary to know what we mean by Risk in software testing. A Risk is the possibility of a negative or undesirable event or outcome. It is basically a possible problem. We need to handle risk because if it happens then it may cause a very negative impact.

Risk based testing is basically a testing done for the project based on risks. It uses risk to prioritize and emphasize the appropriate tests during test execution. In simple terms – Risk is the probability of occurrence of an undesirable outcome. This outcome is also associated with an impact. Since there might not be sufficient time to test all functionality, Risk based testing involves testing the functionality which has the highest impact and probability of failure. Risk-based testing also means managing project risks, which are possible events or outcomes that endanger successful completion of the project.

How to perform risk based testing?

Risk based testing involves both mitigation and contingency:

Mitigation – Mitigation is done to reduce the likelihood of defects.

Contingency – In case if the risk becomes an outcome there should be a plan to reduce the risk impact.

Risk based testing also involves risk analysis to remove or prevent defects by non-testing activities and to select the testing activities to be performed.

For risk based testing you should start with product risk analysis. Techniques used for this are:

Benefits of Risk-based Testing


Although risk-based testing has several advantages, it also includes some disadvantages:

Why do we use Risk-based Testing?



Get A Free Quote