Depending on the time constraint and type of software being tested , there may be a need of risk analysis where we shold focus more on the risky areas of the system. For example : if we consider the online shopping application the most risky area would be the payment page from the user point of view. The end user will be more focused on the transactions as thry will be paying the money directly.
So we need to do risk analysis here.Risk-based testing is the idea that we can organize our testing efforts in a way that reduces the residual level of product risk when the system is deployed.
We also approach this type of testing when we have less time. In that case the risky areas are prioritized first and then testing is performed over them.
Risk base testing is done with the following steps :
(1) Through meetings and plannings the risk analysis is done. The areas having heighest risk is analysed. For this we need to have clear understaing of the specifications.
(2) Proper testing is done to explore and correct each risk. We can choose to brainstorm with the stakeholders.
(3) There may be generation of other risks on correction of other ones while execution. So proper mitigation plans needs to be made for this.
(4) Risk-based testing also includes measurement process that recognizes how well we are working at finding and removing faults in key areas.
Advantages/Benefits of Risk-based testing:
- Improved quality – All of the critical functions of the application are tested. Real time clear understanding of project risk.
- Give more focus on risks of the business project instead of the functionality of the information system.
- Provides a negotiating instrument to client and test manager similar when existing means are limited.
- Associate the product risk to the requirement identifies gaps. During testing, test reporting always takes place in a language (risks) that all stake-holder understands.
- Testing always concentrate on the most important matters first with optimal test delivery, in case of limited time, money and qualified resources. With the time and resources we have, we just can able to complete 100% testing, so we need to determine a better way to accelerate our testing effort with still managing the risk of the application under test. Efforts are not wasted on non-critical or low risk functions.
-Improve customer satisfaction – Due to customer involvement and good reporting and progress trackin
So we need to do risk analysis here.Risk-based testing is the idea that we can organize our testing efforts in a way that reduces the residual level of product risk when the system is deployed.
We also approach this type of testing when we have less time. In that case the risky areas are prioritized first and then testing is performed over them.
Risk base testing is done with the following steps :
(1) Through meetings and plannings the risk analysis is done. The areas having heighest risk is analysed. For this we need to have clear understaing of the specifications.
(2) Proper testing is done to explore and correct each risk. We can choose to brainstorm with the stakeholders.
(3) There may be generation of other risks on correction of other ones while execution. So proper mitigation plans needs to be made for this.
(4) Risk-based testing also includes measurement process that recognizes how well we are working at finding and removing faults in key areas.
Advantages/Benefits of Risk-based testing:
- Improved quality – All of the critical functions of the application are tested. Real time clear understanding of project risk.
- Give more focus on risks of the business project instead of the functionality of the information system.
- Provides a negotiating instrument to client and test manager similar when existing means are limited.
- Associate the product risk to the requirement identifies gaps. During testing, test reporting always takes place in a language (risks) that all stake-holder understands.
- Testing always concentrate on the most important matters first with optimal test delivery, in case of limited time, money and qualified resources. With the time and resources we have, we just can able to complete 100% testing, so we need to determine a better way to accelerate our testing effort with still managing the risk of the application under test. Efforts are not wasted on non-critical or low risk functions.
-Improve customer satisfaction – Due to customer involvement and good reporting and progress trackin
No comments:
Post a Comment