Paper

{
  "raw_xml": "<entry>\n    <id>http://arxiv.org/abs/2602.23957v1</id>\n    <title>The Vocabulary of Flaky Tests in the Context of SAP HANA</title>\n    <updated>2026-02-27T11:59:23Z</updated>\n    <link href='https://arxiv.org/abs/2602.23957v1' rel='alternate' type='text/html'/>\n    <link href='https://arxiv.org/pdf/2602.23957v1' rel='related' title='pdf' type='application/pdf'/>\n    <summary>Background. Automated test execution is an important activity to gather information about the quality of a software project. So-called flaky tests, however, negatively affect this process. Such tests fail seemingly at random without changes to the code and thus do not provide a clear signal. Previous work proposed to identify flaky tests based on the source code identifiers in the test code. So far, these approaches have not been evaluated in a large-scale industrial setting. Aims. We evaluate approaches to identify flaky tests and their root causes based on source code identifiers in the test code in a large-scale industrial project. Method. First, we replicate previous work by Pinto et al. in the context of SAP HANA. Second, we assess different feature extraction techniques, namely TF-IDF and TF-IDFC-RF. Third, we evaluate CodeBERT and XGBoost as classification models. For a sound comparison, we utilize both the data set from previous work and two data sets from SAP HANA. Results. Our replication shows similar results on the original data set and on one of the SAP HANA data sets. While the original approach yielded an F1-Score of 0.94 on the original data set and 0.92 on the SAP HANA data set, our extensions achieve F1-Scores of 0.96 and 0.99, respectively. The reliance on external data sources is a common root cause for test flakiness in the context of SAP HANA. Conclusions. The vocabulary of a large industrial project seems to be slightly different with respect to the exact terms, but the categories for the terms, such as remote dependencies, are similar to previous empirical findings. However, even with rather large F1-Scores, both finding source code identifiers for flakiness and a black box prediction have limited use in practice as the results are not actionable for developers.</summary>\n    <category scheme='http://arxiv.org/schemas/atom' term='cs.SE'/>\n    <published>2026-02-27T11:59:23Z</published>\n    <arxiv:comment>Accepted to ESEM IGC 2023</arxiv:comment>\n    <arxiv:primary_category term='cs.SE'/>\n    <author>\n      <name>Alexander Berndt</name>\n    </author>\n    <author>\n      <name>Zoltán Nochta</name>\n    </author>\n    <author>\n      <name>Thomas Bach</name>\n    </author>\n    <arxiv:doi>10.1109/ESEM56168.2023.10304860</arxiv:doi>\n    <link href='https://doi.org/10.1109/ESEM56168.2023.10304860' rel='related' title='doi'/>\n  </entry>"
}