Risk Based Testing
Submitted by sgunaratne on March 18, 2009 - 1:02am
Risk Based Testing is a hot topic in the testing industry. However, no clear case study or process is defined. The customer needs a specific set of functional requirements to solve a business problem. How do you apply risk based testing if all functional requirements are equally important to the customer?
Good question. risk-based testing is:
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.
So even if all the functions have equal importance, there may not be same level of risk associated with each functionality. For eg:
1) Login
2) Change password
3) Forgot password
4) Catchpa
Now if you are a web application and if you dont provide catchpa you have the high risk of sites being attacked by bots. So find if there is a risk higher then this. If not you need to focus on the Catchpa part.
Here all functions may have equal importance. All features have to work, but the risk of change password not working vs catchpa not working needs to evaluated.
Hope this clarifies.
- Login or register to post comments
Submitted by csqa on March 18, 2009 - 10:38am.