Please use this identifier to cite or link to this item: http://dx.doi.org/10.18419/opus-8944
|Title:||Will my tests tell me if I break this code?|
|metadata.ubs.konferenzname:||International Workshop on Continuous Software Evolution and Delivery (2016, Austin,Tex.)|
|metadata.ubs.publikation.source:||Proceedings of the International Workshop on Continuous Software Evolution and Delivery : CSED '16. New York, NY : ACM, 2016. - ISBN 978-1-4503-4157-8, S. 23-29|
|Abstract:||Automated tests play an important role in software evolution because they can rapidly detect faults introduced during changes. In practice, code-coverage metrics are often used as criteria to evaluate the effectiveness of test suites with focus on regression faults. However, code coverage only expresses which portion of a system has been executed by tests, but not how effective the tests actually are in detecting regression faults. Our goal was to evaluate the validity of code coverage as a measure for test effectiveness. To do so, we conducted an empirical study in which we applied an extreme mutation testing approach to analyze the tests of open-source projects written in Java. We assessed the ratio of pseudo-tested methods (those tested in a way such that faults would not be detected) to all covered methods and judged their impact on the software project. The results show that the ratio of pseudo-tested methods is acceptable for unit tests but not for system tests (that execute large portions of the whole system). Therefore, we conclude that the coverage metric is only a valid effectiveness indicator for unit tests.|
|Appears in Collections:||05 Fakultät Informatik, Elektrotechnik und Informationstechnik|
Items in OPUS are protected by copyright, with all rights reserved, unless otherwise indicated.