I’ve seen a few patterns over the years: retries everywhere, quarantining tests, rewriting flows, adding more waits than anyone feels good about, or just slowly losing trust in CI signal. None of them feel great once you have hundreds or thousands of tests running across multiple environments.
I’m especially interested in how QA and engineering teams split responsibility. Do you treat flakiness as a test problem, a product problem, or infrastructure noise? At what point do you decide a test is no longer worth keeping?
Asking partly out of personal frustration and partly because I’ve been working on tooling around browser automation and want to sanity check the problems I’m seeing against the pains others are feeling day to day.
Would love to hear real stories from people running E2E at scale, what actually worked, and what you wish you had done earlier.
Thanks in advance.
benoau•1h ago