Checked Coverage for Test Suite Reduction – Is It Worth the Effort?

As the size of software projects increases, their test suites usually grow accordingly. Test suite size, however, has a direct impact on the efficiency of software testing. Hence, test suite reduction (TSR) procedures aim at removing redundant test cases while maintaining the suites fault detection capabilities (FDC). This paper explores checked coverage as a coverage metric for TSR; checked coverage not only investigates if a part of code was executed but also if it was checked by a test oracle. Previously, this metric has been applied successfully as an indicator for oracle quality. To assess how suitable checked coverage is in comparison to traditional metrics, such as line or method coverage, we developed a TSR tool for Java programs. In an empirical evaluation, we performed TSR based on different reduction algorithms, coverage metrics, and open-source Java projects. Our study investigates both the efficiency of the TSR as well as effectiveness in regard to the FDC and size of the reduced test suites. CCS CONCEPTS • Software and its engineering → Software testing and debugging. ACM Reference Format: Roxane Koitz-Hristov, Lukas Stracke, and Franz Wotawa. 2022. Checked Coverage for Test Suite Reduction–Is It Worth the Effort?. In IEEE/ACM 3rd International Conference on Automation of Software Test (AST'22), May 17-18, 2022, Pittsburgh, PA, USA. ACM, New York, NY, USA, 11 pages. https://doi.org/10.1145/3524481.3527216