Risk-Based Testing: Identifying, Assessing, Mitigating & Managing Risks Efficiently in Software Testing

Abstract

Most of the software organizations often strive hard while deciding the release dates of their software product. This is because no organization wants to take risks where the fault is revealed in the developed product on the client-side. This will lead to expensive bug-fixes, and the image of the developer company is tarnished. On the other hand, testing beyond a particular time would lead to a loss of revenue for the organization. The effective approach for handling the risky components will enable software testers to identify more important test cases that can reveal faults associated with those components. After identification of those test cases, software testers work to fix fault sooner by managing the testing schedule by running such test cases earlier. Faults associated with hazardous components can also be detected sooner. In risk based testing, the probability of a fault becoming a reality is assessed, and the damage that this fault can cause when leading to failure is considered. This study has presented an overall layout of risk-based testing. We have summarized the research findings of numerous researchers in this field. This will help the newcomers in this filed to provide a comprehensive source of information altogether. The future direction of this study will focus on proposing a novel technique for risk-based testing, considering different parameters together.