What is Risk Based Testing?

Share The Knowledge. It Grows !!!


Have you ever developed the test plan or test strategy for you project? Or have you ever gone through it for you project? Then you must have seen the Risk section in those plans. Risk is nothing but the problem that may come across the path of software development. It is also possible that problem may not occur at all. We are not sure about the occurrence of the problem still we need to prepare for the potential problem that project may face going forward.


Below is the few types of risk and they’re few example.

1.        Risks associated with Software Requirement Document

Poorly defined requirement

Ambiguity in requirement document

Requirement changes frequently


2.        Risks associated with the cost of the project.

Unrealistic and bad estimation

Hardware failure

Lack of standard in coding and testing


3.        Risks associated with Time and Schedule

Not having proper knowledge of technology

Lack of required technical skilled employee

Tool failure and environment changes


4.        Risks associated with quality

Incomplete or ambiguity in requirement document

Collaboration between development team and testing team

Complexity of project


5.        Risks associated with Business

Failure in budget and commitment

Business does not have selling strategy of the new product.

Product crossed the time line and now no one wants that product.


Here we have understood the different type of risks available during the software development.


Why Risk Based Testing?

As we know testing is the process which starts quite late and under pressure. Also, it won’t make sense to quite the testing and release the product without testing. At the same time, we can’t think of the delay in the delivery of the product. So, what will be your strategy in such a situation? The industry has an answer for this question. Here we will follow Prioritize based testing efforts called as Risk-Based testing.


So how you will prioritize your testing task?

  • Test coverage needs to define
  • Define product and process risk
  • Mention the identified risk in Test Plan
  • Create traceability matrix for better overview of the coverage
  • Calculate the probability and its impact on product for every risk
  • Prioritize all risk items according to its value
  • Design the risk-based test suite
  • Conduct risk review time to time


Share The Knowledge. It Grows !!!

Leave a Reply

Your email address will not be published.

Ops!! You Can not Copy from The Digital Mentor.