Flaky tests quietly drain engineering teams. You hit re-run, the test passes, and move on — but that pattern compounds across the team.
I'm building Culprit (a tool that watches your CI, finds flaky tests, and bisects to the introducing commit automatically), and I'm running a short 5-question survey to put real numbers on the cost before we set pricing.
If your team deals with flaky CI, I'd appreciate 3 minutes. Drop answers in the comments, or email culprit@megaloop.app with subject "CI survey".
The 5 questions
Q1 – Your role:
