From c12b783aaf392e33e1531293db31de6578109bb9 Mon Sep 17 00:00:00 2001 From: Jiaxun Wei Date: Wed, 26 Aug 2026 22:40:25 +0200 Subject: [PATCH 1/2] Scientific paper proposal: FlakyGuard (ASE 2025), week 2 --- .../week2/jiaxun-kozar/README.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 contributions/scientific-paper/week2/jiaxun-kozar/README.md diff --git a/contributions/scientific-paper/week2/jiaxun-kozar/README.md b/contributions/scientific-paper/week2/jiaxun-kozar/README.md new file mode 100644 index 000000000..30f4bc82e --- /dev/null +++ b/contributions/scientific-paper/week2/jiaxun-kozar/README.md @@ -0,0 +1,26 @@ +# Assignment Proposal + +## Title + +FlakyGuard: Automatically Fixing Flaky Tests at Industry Scale (ASE 2025) + +## Names and KTH ID + + - Jiaxun Wei (jiaxun@kth.se) + - Matyas Kozar (kozar@kth.se) + +## Deadline + +- Week 2 + +## Category + +- Scientific paper + +## Description + +We want to present the ASE 2025 paper ["FlakyGuard: Automatically Fixing Flaky Tests at Industry Scale"](https://doi.org/10.1109/ASE63991.2025.00179) by Li, Behrang, Shi, and Liu. The authors propose a tool called FlakyGuard that automatically repairs flaky tests, and they evaluate it in production at Uber. We plan to focus on how FlakyGuard traverses a call graph to collect just enough context, discuss the reported success rate together with how many fixes actually land in production, and contrast the approach with previous work in this field. + +**Relevance** + +Flaky tests break the assumption that a failing build means the code is broken. When working with flaky tests, developers prefer to rerun jobs rather than investigate the failure, and over time the test suite loses its value. Therefore, fixing them automatically is directly relevant to the subject of test automation and CI. From 8a5411bcd86e4b12614bdb2551a1ea797e72c1bb Mon Sep 17 00:00:00 2001 From: Jiaxun Wei Date: Fri, 28 Aug 2026 14:23:19 +0200 Subject: [PATCH 2/2] Update README.md Co-authored-by: Aman Sharma --- contributions/scientific-paper/week2/jiaxun-kozar/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributions/scientific-paper/week2/jiaxun-kozar/README.md b/contributions/scientific-paper/week2/jiaxun-kozar/README.md index 30f4bc82e..e12b09962 100644 --- a/contributions/scientific-paper/week2/jiaxun-kozar/README.md +++ b/contributions/scientific-paper/week2/jiaxun-kozar/README.md @@ -19,7 +19,7 @@ FlakyGuard: Automatically Fixing Flaky Tests at Industry Scale (ASE 2025) ## Description -We want to present the ASE 2025 paper ["FlakyGuard: Automatically Fixing Flaky Tests at Industry Scale"](https://doi.org/10.1109/ASE63991.2025.00179) by Li, Behrang, Shi, and Liu. The authors propose a tool called FlakyGuard that automatically repairs flaky tests, and they evaluate it in production at Uber. We plan to focus on how FlakyGuard traverses a call graph to collect just enough context, discuss the reported success rate together with how many fixes actually land in production, and contrast the approach with previous work in this field. +We want to present the ASE 2025 paper ["FlakyGuard: Automatically Fixing Flaky Tests at Industry Scale"](https://doi.org/10.1109/ASE63991.2025.00179) by Li, Behrang, Shi, and Liu. The authors propose a tool called FlakyGuard that automatically repairs flaky tests, and they evaluate it in production at Uber. We plan to focus on how FlakyGuard traverses a call graph to collect just enough context to resolve flakiness, discuss the reported success rate together with how many fixes actually land in production, and contrast the approach with previous work in this field. **Relevance**