Tests that fail inconsistently, without changes to the code under test, are described as flaky.
Flaky tests do not give a clear indication of the presence of software bugs and thus limit the …

A flaky test is a test case whose outcome changes without modification to the code of the test
case or the program under test. These tests disrupt continuous integration, cause a loss of …

Various mature automated test generation tools exist for statically typed programming
languages such as Java. Automatically generating unit tests for dynamically typed …

Gradual typing enables developers to annotate types of their own choosing, offering a
flexible middle ground between no type annotations and a fully statically typed language. As …

Non-deterministically passing and failing test cases, so-called flaky tests, have recently
become a focus area of software engineering research. While this research focus has been …

Regression testing can greatly help in software development, but it can be seriously
undermined by flaky tests, which can both pass and fail, seemingly nondeterministically, on …

Flaky tests are test cases that can pass or fail without code changes. They often waste the
time of software developers and obstruct the use of continuous integration. Previous work …

Flaky tests (tests with non-deterministic outcomes) can be problematic for testing efficiency
and software reliability. Flaky tests in test suites can also significantly delay software …

Flaky tests are tests that yield different outcomes when run on the same version of a
program. This non-deterministic behaviour plagues continuous integration with false signals …

Developers typically run tests after code changes. Flaky tests, which are tests that can
nondeterministically pass and fail when run on the same version of code, can mislead …