Last updated on Monday, October 06, 2025
@inproceedings{Kisaakye2024ICTSS,
author = {Kisaakye, Joanna and Beyaz{\i}t, Mutlu and
Demeyer, Serge},
booktitle = {Proceedings {ICTSS 2024} (International Conference on
Testing Software and Systems)},
editor = {Men{\'e}ndez, H{\'e}ctor D. and Bello-Orgaz, Gema and
Barnard, Pepita and Bautista, John Robert and
Farahi, Arya and Dash, Santanu and Han, DongGyun and
Fortz, Sophie and Rodriguez-Fernandez, Victor},
title = {Extending a Flakiness Score for System-Level Tests},
year = {2024},
abstract = {Flaky tests (i.e. automated tests with a
non-deterministic test outcome) undermine the
trustworthiness of today's DevOps build-pipelines,
and recent research has investigated ways to detect
or even remove flaky tests. In contrast, others
proclaim that test engineers should ``Assume all
Tests Are Flaky'' because, in today's
build-pipelines, one can never fully control all
components of the system under test. Test engineers
then capture the randomness of test results via what
is called a flakiness score. In this paper, we extend
an existing flakiness score to deal with system-level
tests. We illustrate, via simulated test outcomes,
how this refined score can support three different
strategies for dealing with flaky tests---(i) Rerun,
(ii) Fix and (iii) Monitor.},
annote = {internationalconference},
doi = {10.1007/978-3-031-80889-0_20},
}