Empirical studies of test‐suite reduction
Software Testing, Verification and Reliability · 2002-12 · 12 (4) · 219-249
DOI: 10.1002/stvr.256 ↗Kurz gefasst
Fachartikel in der Zeitschrift Software Testing, Verification and Reliability, online erschienen am 04.12.2002. Verfasst von Gregg Rothermel und 3 weiteren Autor:innen. Die Arbeit wurde bisher 190-mal zitiert (Crossref) und nennt 21 Literaturangaben.
Abstract (Originalsprache)
Test‐suite reduction techniques attempt to reduce the costs of saving and reusing test cases during software maintenance by eliminating redundant test cases from test suites. A potential drawback of these techniques is that reducing the size of a test suite might reduce its ability to reveal faults in the software. Previous studies have suggested that test‐suite reduction techniques can reduce test‐suite size without significantly reducing the fault‐detection capabilities of test suites. These studies, however, involved particular programs and types of test suites, and to begin to generalize their results, further work is needed. This paper reports on the design and execution of additional studies, examining the costs and benefits of test‐suite reduction, and the factors that influence these costs and benefits. In contrast to previous studies, results of these studies reveal that the fault‐detection capabilities of test suites can be severely compromised by test‐suite reduction. Copyright © 2002 John Wiley & Sons, Ltd.
Zitieren
APA
Rothermel, G., Harrold, M. J., Ronne, J. V., & Hong, C. (2002). Empirical studies of test‐suite reduction. Software Testing, Verification and Reliability, 12(4), 219-249. https://doi.org/10.1002/stvr.256
Vancouver
Rothermel G, Harrold MJ, Ronne JV, Hong C. Empirical studies of test‐suite reduction. Software Testing, Verification and Reliability. 2002;12(4):219-249. doi:10.1002/stvr.256
BibTeX
@article{Rothermel2002,
author = {Rothermel, Gregg and Harrold, Mary Jean and Ronne, Jeffery von and Hong, Christie},
title = {Empirical studies of test‐suite reduction},
journal = {Software Testing, Verification and Reliability},
year = {2002},
volume = {12},
number = {4},
pages = {219--249},
doi = {10.1002/stvr.256}
}
EUVIMED