Tag
An engineering blog post from Buildkite details how a flaky test led to the discovery of a use-after-free bug in the redis-client Ruby library, describing the debugging process and root cause analysis.
Describes a loop command in Cursor to automatically fix flaky tests by running the test suite multiple times, collecting intermittent failures, and fixing or quarantining them until five consecutive green runs.
The article discusses the problem of flaky tests in software development and proposes a simple mechanical habit: when using a merge queue, continue to run the full test suite on main and maintain a visible list of recent main failures to help identify and eradicate flaky tests.