paperbot · PL 论文追踪

全部论文 待读 收藏

P2 D <scp>e</scp> F <scp>laker</scp>

DeFlaker
ICSE Proceedings of the 40th International Conference on Software Engineering2018匹配度 2/10 · 该论文关注 flaky test 检测与软件测试调试，属于测试/调试与修复方向，但并未涉及用户核心关注的静态分析、LLM/Agent、浮点程序分析或贝叶斯程序分析。其方法与用户研究画像交叉点很少，仅可归入广义程序分析/软件工程工具。引用 171 inbox
Jonathan Bell, Owolabi Legunsen, Michael Hilton, Lamyaa Eloussi, Tifany Yung, Darko Marinov
测试、调试与修复
crossref: 2026-09-12

AI 速览

一句话：提出 DeFlaker，旨在高效检测与最新代码修改无关的 flaky test，避免昂贵的重复运行。

开发者常通过运行测试来确认最新修改未破坏已有功能。理想情况下，新出现的测试失败对应回归；但部分失败源于测试的非确定性，即 flaky test，与最新修改无关。检测 flaky test 的典型方法是反复重跑失败测试，但这一过程开销大，会拖慢开发周期。本文提出 DeFlaker，针对该问题展开研究。摘要未给出具体方法与评估细节，仅说明其目标是更高效地识别 flaky test。

问题
开发者需要区分由最新修改引起的回归失败与由测试非确定性（flaky）导致的失败，而反复重跑失败测试来检测 flaky test 代价高且拖慢开发周期。
方法
摘要未给出具体技术方案；从标题可知论文提出 DeFlaker 来检测 flaky test。
评估
摘要未给出评估信息。
原文摘要（Abstract）

Developers often run tests to check that their latest changes to a code repository did not break any previously working functionality. Ideally, any new test failures would indicate regressions caused by the latest changes. However, some test failures may not be due to the latest changes but due to non-determinism in the tests, popularly called flaky tests. The typical way to detect flaky tests is to rerun failing tests repeatedly. Unfortunately, rerunning failing tests can be costly and can slow down the development cycle.

链接与引用

DOI 原文 · PDF（开放获取） ·

BibTeX 
@inproceedings{paperbot4495,
  title = {D
            <scp>e</scp>
            F
            <scp>laker</scp>},
  author = {Jonathan Bell and Owolabi Legunsen and Michael Hilton and Lamyaa Eloussi and Tifany Yung and Darko Marinov},
  booktitle = {ICSE},
  year = {2018},
  doi = {10.1145/3180155.3180164}
}