Integrating software quality models into risk-based testing

Abstract

Risk-based testing is a frequently used testing approach which utilizes identified risks of a software system to provide decision support in all phases of the testing process. Risk assessment, which is a core activity of every risk-based testing process, is often done in an ad hoc manual way. Software quality assessments, based on quality models, already describe the product-related risks of a whole software product and provide objective and automation-supported assessments. But so far, quality models have not been applied for risk assessment and risk-based testing in a systematic way. This article tries to fill this gap and investigates how the information and data of a quality assessment based on the open quality model QuaMoCo can be integrated into risk-based testing. We first present two generic approaches showing how quality assessments based on quality models can be integrated into risk-based testing and then provide the concrete integration on the basis of the open quality model QuaMoCo. Based on five open source products, a case study is performed. Results of the case study show that a risk-based testing strategy outperforms a lines of code-based testing strategy with regard to the number of defects detected. Moreover, a significant positive relationship between the risk coefficient and the associated number of defects was found.

Un mapeo sistemático de literatura: pruebas basadas en riesgo en el desarrollo de software

“…In the time window established and presented in Figure 1, since year 2000 onwards, there is an increasing interest in RBT, with research increasing from 2012 to the present. The percentage of studies according to the classification type per year is: (i) 22.7% corresponding to approaches: 2012 (30) , 2017 (14) , 2018 (22) , 2020 (32,33) ; (ii) 18.2% corresponds to case study: 2000 (21) , 2010 (29) , 2014 (2) , 2016 (12) ; (iii) 9.1% corresponds to Taxonomy: 2014 (9) , 2019 (4) ; (iv) 9.1% corresponds to Techniques: 2005 (26) , 2018 (28) . (v) 40.9% corresponds to one article per year in Framework 2014 (27) , Tools 2007 (31) , Method 2016 (8) , Methodology 2013 (25) , Model 2012 (13) , Prediction of Defects 2016 (23) , Procedure 2014 (7) , Process 2010 (10) and Exploratory Review 2016 (24) .…”

“…It is an approach that consists of a set of activities related to the identification (5) 1 7,1 of risk factors related to software requirements. (14,22,30) Approach…”

Testing in a DevOps Era: Perceptions of Testers in Norwegian Organisations

“…The main goal is to prevent and eliminate coding errors before the application has reached production. This also calls for more risk-based testing [22,12,11] processes, and less test-case oriented testing. The testing becomes more focused on minimising the risk of critical errors in production, and continuously assessing the impacts on costs related to testing.…”

“…More empirical work must to be conducted to understand which approaches work where. We also need to evolve risk-based testing, and achieve wider-spread use in industry [22,12,11]. We need a better understanding of how to achieve a better return of investment of DevOps practices and principles depending on the context.…”

Tools, Strategies & Models for Incorporating Software Quality Assurance in Risk Oriented Testing

“…Taxonomies for check listing the quality requirements and overall quality assessment metrics can be formulated 19 .…”