Risk-Based Testing

Risk based testing is basically a testing done for the project based on risks. It uses risk to prioritize and emphasize during test execution.

In other words, risk is the probability of occurrence of an undesirable outcome. 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.

https://www.youtube.com/watch?v=tQOyHlgERb4

Facts of Risk-Based Testing

  • Risk-based testing starts early in the project, identifying risks to system quality and using that knowledge of risk to guide testing planning, specification, preparation and execution.
  • Risk-based testing involves mitigation. Hence, testing to provide opportunities to reduce the likelihood of defects. Especially high-impact defects. It also involves contingency, where testing identifies work-around to make the defects that do get past us less painful.
  • Risk-based testing also involves measuring how well we are doing at finding and removing defects in critical areas.
  • Risk-based testing can also involve using risk analysis to identify proactive opportunities to remove or prevent defects through non-testing activities and to help us select which test activities to perform.

Steps In Performing Risk-Based Testing

  1. Make a prioritized list of risks.
  2. Perform testing that explores each risk.
  3. As risks evaporate and new ones emerge, adjust your test effort to stay focused on the current crop.

Objectives of Risk-Based Testing

  • To identify when and how to use Risk Based Testing.
  • Understand advantages and disadvantages of Risk Based Testing.
  • To understand steps of implementing of Risk Based Testing on appropriate application.
  • Make risk-free project using best practices in risk management to achieve a project outcome that balances risks with quality, features, budget and schedule.

Major Processes to Describe Risk-Based Testing

Process 1

Describe all requirements in terms of Risk involved in the project. The stake holders are basically a mixture of business and technical team. Stake holders involve various people from various departments for instance, the client, customers, business experts, technical experts, project manager, project Leader, users, developers and infrastructure representative.

Process 2

In terms of risk assessment, prioritize the requirements. Once all the possible risks and their impacts are analyzed, the project manager has to get the requirements prioritized. Priority of the requirements should be agreed upon and should be updated in functional requirement document.

Process 3

Plan and define tests according to requirement prioritization. After getting the Requirement with the priority tagged, we can start the test activities with keeping the priority of the requirements in mind.

Process 4

Execute test according to prioritization and acceptance criteria.If any of the identified risk realizes by the time of “Test execution Schedule”, then there is quite good chances of schedule slippage from development side. In this situation, again, Test manager has to apply the Pareto principle and finalizes the scope of testing in the reduced timeline that will ensure least risk and highest quality.

Risk-Based Testing

To Close Up

Risk based testing is type of software testing. It focuses on the features and functions to be tested based of priority, importance and potential failures. First we identify the risk to the project, we analyze the risk associated with the potential cost of the projects.

It is a testing process with unique features. It is basically for those project and application that is based on risk. Using risk, Risk based testing prioritize and emphasize the suitable tests at the time of test execution. In other word, Risk is the chance of event of an unwanted outcome. This unwanted outcome is also related with an impact.

 

Rate this post

Leave a Reply

Your email address will not be published. Required fields are marked *