Evaluating NonDex for Modern Java Ecosystem
This program is tentative and subject to change.
This paper investigates the updated NonDex on modern Java projects. We identified 1590 flaky tests in 36 Maven projects and 1384 flaky tests in 35 Gradle projects. Comparing these findings to prior work, this study highlights a substantial increase for a modern Java project to contain some flaky test(s). We also studied the propagation of ID flakiness through project dependencies and fixed a key non-determinism issue in the Gradle build system itself. Our study emphasizes the importance of proactively employing NonDex to detect and fix flaky tests, preventing potential disruptions in ongoing and future projects relying on its capabilities. We put all our results in an anonymized repository publicly available at https://github.com/NonDexFTW/NonDex-Experiments.
This program is tentative and subject to change.
Sun 27 AprDisplayed time zone: Eastern Time (US & Canada) change
14:00 - 15:30 | |||
14:00 22mPaper | Evaluating NonDex for Modern Java Ecosystem FTW Kaiyao Ke University of Illinois at Urbana-Champaign, Darko Marinov University of Illinois at Urbana-Champaign | ||
14:22 22mTalk | On the Perception and Adoption of Flakiness Scores FTW Joanna Kisaakye , Mutlu Beyazıt University of Antwerp and Flanders Make vzw, Serge Demeyer University of Antwerp and Flanders Make vzw | ||
14:45 22mPaper | Reduction of Test Re-runs by Prioritizing Potential Order Dependent Flaky Tests FTW Hasnain Iqbal University of Dhaka, Zerina Begum University of Dhaka, Kazi Sakib Institute of Information Technology, University of Dhaka | ||
15:07 22mPanel | Mini Panel 2 FTW |