In risk-based testing, the selection of test conditions is guided by the risks identified to product quality. These product quality risks also are used to determine the allocation of effort for the testing the test conditions and for prioritizing the created test cases.
When defects are identified before product release, testing has reduced quality risk by identifying the defects and providing methods to handle them.
Here are some examples of quality risks:
- Delayed response to users action: Non-functional risk pertaining to performance
- Reports with the wrong result or incorrect calculations: Functional risk pertaining to precision
- Complicated UI and input fields: Non-functional risk pertaining to usability & system adoption
The stakeholders can use any methods given below to identify risks:
How to identify risks?
- Making independent reviews
- Existing templates of risks
- Retrospective meetings in projects
- Conducting risk workshops
- Brainstorming with all stakeholders
- Creating and using checklists
After risks have been identified, evaluation of identified risks is done.
Risk assessment usually involves these activities:
- Classifying each risk
- Identifying the probability of each risk occurring
- Impact of each risk
- Identifying or assigning risk properties like risk owner
Risks in product quality can be minimized even before execution of test case begins.