Risk and Testing
- 2. Nola Cita Putri 11453205405 Program Studi S1 Sistem Informasi Fakultas Sains dan teknologi Universitas Islam Negeri Sultan Syarif Kasim Riau 2017 “RISK AND TESTING” Program Studi S1 Sistem Informasi Fakultas Sains dan Teknologi Universitas Islam Negeri Sultan Syarif Kasim Riau 2017
- 3. Risks and Levels of Risk Risk is a word we all use loosely. In the future, a risk has some likelihood between 0% and 100%; it is a possibility, not a certainty. In the past, however, either the risk has materialized and become an outcome or issue or it has not; the likelihood of a risk in the past is either 0% or 100%.
- 4. Product risk as the possibility that the system or software might fail to satisfy some reasonable customer, user, or stakeholder expectation. Product Risks
- 5. 1 2 3 4 5 6 Which might not be functionality Rather security Reliability Usability Maintainability or performance Unsatisfactory software might have problems : Particular quality characteristic
- 6. Risk-based Testing Risk-based testing uses risk to prioritize and emphasize the appropriate tests during test execution. Risk-based testing starts early in the project, identifying risks to system quality and using that knowledge of risk to guide testing planning. Risk-based testing involves both mitigation - testing to provide opportunities to reduce the likelihood of defects. 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. 1 2 3 4 5
- 7. The origin of the risk-based testing concept Product Risk Analysis Reading of the Requirements Design Specifications User Documentation and Other Items
- 8. Project risks that apply to testing, we can use the same concepts we apply to identifying, prioritizing and managing product risks. Project Risks
- 9. Mitigate Take steps in advance to reduce the likelihood (and possibly the impact) of the risk Have a plan in place to reduce the impact should the risk become an outcome Convince some other member of the team or project stakeholder to reduce the likelihood or accept the impact of the risk Do nothing about the risk, which is usually a smart option only when there's little that can be done or when the likelihood and impact are low Contingency Transfer Ignore
- 10. Typical risks along with some options for managing : Logistics or product quality problems that block tests These can be miti gated through careful planning, good defect triage and management, and robust test design Test items that won't install in the test environment: These can be mitigated through smoke (or acceptance) testing prior to starting test phases or as part of a nightly build or continuous integration. Excessive change to the product that invalidates test results or requires updates to test cases, expected results and environments These can be mit igated through good change-control processes, robust test design and light weight test documentation Insufficient or unrealistic test environments that yield misleading results One option is to transfer the risks to management by explaining the limits on test results obtained in limited environments 1 2 3 4
- 11. Additional risks to consider and perhaps to manage : Organizational issues such as shortages of people, skills or training, problems with communicating and responding to test results, bad expec tations of what testing can achieve and complexity of the project team or organization Supplier issues such as problems with underlying platforms or hardware, failure to consider testing issues in the contract or failure to properly respond to the issues when they arise Technical problems related to ambiguous, conflicting or unprioritized requirements, an excessively large number of requirements given other project constraints, high system complexity and quality problems with the design, the code or the tests 1 2 3
- 12. Tying it all together for risk management • One common problem people have when organizations first adopt riskbased testing is a tendency to be excessively alarmed by some of the risks once they are clearly articulated. • Manage risks appropriately, based on likelihood and impact. Triage the risks by understanding how much of your overall effort can be spent dealing with them • Focus on the point of the exercise. As with life, the goal of risk-based testing should not be - cannot practically be - a risk-free project • We can accomplish with risk-based testing is the marriage of testing with best practices in risk management to achieve a project outcome that balances risks with quality, features, budget and schedule.
- 13. Backlink Website Kampus UIN Suska Riau JL. H.R Soebrantas No.155 KM.35 Simpang Baru Panam Pekanbaru-Riau. http://sif.uin-suska.ac.id/ http://faste.uin-suska.ac.id/ http://www.uin-suska.ac.id/
- 14. Thank You!