Scientific paper proposal: FlakyGuard (ASE 2025), week 2 - #2935
Open
LeuisKen wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
FlakyGuard: Automatically Fixing Flaky Tests at Industry Scale (ASE 2025)
Names and KTH ID
Deadline
Category
Description
We want to present the ASE 2025 paper "FlakyGuard: Automatically Fixing Flaky Tests at Industry Scale" 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.