Risk-Based Testing And Its Benefits

We tester always keep ourselves busy in Testing but always try to avoid project & project risk through Risk Based Testing. When ever testing starts, test cases of complex module and test cases with high priority are chosen to test first and as being the tester, quality of product is the most important task…since Software industry is notorious for delay in product delivery that not only impose some extra cost,but also impact the reputation and revenue because of some fine impose by Client and there are thousand of examples in Industry and there is a long list of reputed companies who have paid for delaying for delivary once or on several occasions. These uncertain events cause undesirable consequences so are termed as Risk

Definition of Risk(ISTQB Syllabus)

Risk can be defined as the chance of an event, hazard,threat or situation occurring and resulting in undesirable consequences or a potential problem. A risk has two main part

  1. Probability
  2. Loss:

Graphical representation


Risk is calculated on the basis of  loss and Probability of failure

Risk = Loss*Probability

Due to this before starting any project, Software companies try  Risk Management, to identify, control and minimize the impact caused by risk. In this future plans are made to mitigate the loss along with the probability of occurrence of risk. Picture below will help in understanding Risk Management.

Risk Management

Risk based testing approach provides a very proactive opportunity to reduce the level of Risk associated with product and for this early testing helps alot, it provides opportunity to show the risk associated with project and it also helps to test those module first with whom risk is associated while Stakeholder has given a low priority. Once all Risk are identified, these information are used to

1- Identify the test technique

2- Extent of testing on various module

3- Priority of test cases and also help in writing specific Defect bases test cases that are kept as important check list in every Iterations

4- find out the quality of resource and need of training

Since we are talking about Risk then we should also discuss about the typical Risk area

1- Project Risks:
Project risk is the risk that gives blow to the product schedule and increases cost.  Typical factors of project risks are

1- Problems in defining correctRequirement

2- Infeasible requirement that can’t be met

3- Test Environment is not ready and shortage of skill, trained human resources.

4– Objective of project is not defined properly

5- Unrealistic schedule

6- Low quality of Design, coding, testing

7- Wrong selection of technology

2- Product Risks:
Failure area in software is called Product Risk.Factors responsible for product failure are

1- Leaving bugs in product with out fix

2- Failure prone product is delivered to market and client

3- Low compatibility of software with hardware could cause loss of resources and human too.

4- Launching immature product in Market that leaves product out of competition

5- Product that is not made on requirement and are not tested well

Related Articles

5 comments

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.