How CodeInstances Keeps the Failing Run of a Flaky CI Test

Sun, 18 Oct 2026 00:00:00 +0000

Here’s a situation most teams know. An integration test fails about one run in twenty. It calls an API that usually answers one way and occasionally answers another (a field missing, a list in a different order, a slow page that times out). Somebody hits rerun, it goes green, and the failure is gone. A week later it happens again, and the ticket still says “can’t reproduce”.

The trouble is that the one run worth looking at is the one nobody kept. Logs say the test failed. They don’t hold the answer that made it fail.

Flaky Tests on CodeInstances.com

How CodeInstances Keeps the Failing Run of a Flaky CI Test