Integrating inspection and test processes based on context‐specific assumptions. Issue 4 (30th August 2012)

• Record Type: Journal Article
• Authors: Elberzhager, Frank; Münch, Jürgen; Rombach, Dieter; Freimut, Bernd; Raffo, David; Pfahl, Dietmar; Zhang, Li
• Is Part Of: Journal of software. Volume 26:Issue 4(2014:Apr.)
• Page Start: 371
• Page End: 385
• Publication Date: 2012-08-30
• Subjects: Software engineering -- Periodicals; Computer software -- Development -- Periodicals; Software maintenance -- Periodicals; 005.1
• DOI: 10.1002/smr.1569
• Languages: English
• ISSNs: 2047-7473

Abstract

<abstract abstract-type="main"> <title>ABSTRACT</title> <p>Inspections and testing are two of the most commonly performed software quality assurance processes today. Typically, these processes are applied in isolation, which, however, fails to exploit the benefits of systematically combining and integrating them. In consequence, tests are not focused on the basis of early defect detection data. Expected benefits of such process integration include higher defect detection rates or reduced quality assurance effort. Moreover, when conducting testing without any prior information regarding the system's quality, it is often unclear how to focus testing. A systematic integration of inspection and testing processes requires context‐specific knowledge about the relationships between inspections and testing. This knowledge is typically not available and needs to be empirically identified and validated. Often, context‐specific assumptions can be seen as a starting point for generating such knowledge. On the basis of the integrated inspection and testing approach, In²Test, which uses inspection data to focus testing, we present in this article how knowledge about the relationship between inspections and testing can be gained, documented, and evolved in an analytical or empirical manner. In addition, this article gives an overview of related work and highlights future research directions. Copyright © 2012 John Wiley &amp; Sons, Ltd.</p> </abstract>