Analyzing the relationships between inspections and testing to provide a software testing focus |
| |
| Affiliation: | 1. Fraunhofer Institute for Experimental Software Engineering (IESE), Fraunhofer-Platz 1, 67663 Kaiserslautern, Germany;2. University of Helsinki, P.O. Box 68, Gustaf Hällströmin katu 2b, 00014 Helsinki, Finland;3. Vector Informatik GmbH, Ingersheimer Straße 24, 70499 Stuttgart, Germany;1. Department of Emergency Medicine, Emory University School of Medicine, Atlanta, GA;2. Associate Clinical Professor of Surgery, Icahn School of Medicine at Mount Sinai, New York, NY;1. Technology Center of Software Engineering, Institute of Software, Chinese Academy of Sciences, Beijing 100190, China;2. Graduate University, Chinese Academy of Sciences, Beijing 100190, China;3. State Key Laboratory of Computer Science, Beijing 100190, China;1. School of Chemistry and Chemical Engineering, University of Inner Mongolia, Hohhot 010021, China;2. College of Pharmacology, Inner Mongolia Medical University, Hohhot 010059, China;3. Department of Physical Chemistry, University of Science and Technology Beijing, Beijing 100083, China |
| |
| Abstract: | ContextQuality assurance effort, especially testing effort, is frequently a major cost factor during software development. Consequently, one major goal is often to reduce testing effort. One promising way to improve the effectiveness and efficiency of software quality assurance is the use of data from early defect detection activities to provide a software testing focus. Studies indicate that using a combination of early defect data and other product data to focus testing activities outperforms the use of other product data only. One of the key challenges is that the use of data from early defect detection activities (such as inspections) to focus testing requires a thorough understanding of the relationships between these early defect detection activities and testing. An aggravating factor is that these relationships are highly context-specific and need to be evaluated for concrete environments.ObjectiveThe underlying goal of this paper is to help companies get a better understanding of these relationships for their own environment, and to provide them with a methodology for finding relationships in their own environments.MethodThis article compares three different strategies for evaluating assumed relationships between inspections and testing. We compare a confidence counter, different quality classes, and the F-measure including precision and recall.ResultsOne result of this case-study-based comparison is that evaluations based on the aggregated F-measures are more suitable for industry environments than evaluations based on a confidence counter. Moreover, they provide more detailed insights about the validity of the relationships.ConclusionWe have confirmed that inspection results are suitable data for controlling testing activities. Evaluated knowledge about relationships between inspections and testing can be used in the integrated inspection and testing approach In2Test to focus testing activities. Product data can be used in addition. However, the assumptions have to be evaluated in each new context. |
| |
| Keywords: | Inspection Testing Integration Case study |
| 本文献已被 ScienceDirect 等数据库收录！ |
|
