DeFlaker: automatically detecting flaky tests

Jonathan Bell, Owolabi Legunsen, Michael Hilton, Lamyaa Eloussi, Tifany Yung, Darko Marinov

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.

BibTeX

@inproceedings{Bell-al:ICSE18,
  author    = {Jonathan Bell and
               Owolabi Legunsen and
               Michael Hilton and
               Lamyaa Eloussi and
               Tifany Yung and
               Darko Marinov},
  title     = {{DeFlaker:} automatically detecting flaky tests},
  booktitle = {ICSE},
  pages     = {433--444},
  publisher = {{ACM}},
  year      = {2018},
}

DeFlaker: automatically detecting flaky tests

Abstract

Related papers