Fishbone the Flake
Use fishbone categories to separate plausible causes of a flaky test before selecting a fix.
The account-upgrade end-to-end test fails about one run in ten. The visible symptom is a missing confirmation banner after payment submission. Fishbone cause categories: Methods, Data, Environment, Product, Tooling, People/Process The common trap is treating the first visible symptom as the cause. A missing banner looks like a wait problem, but it may be caused by shared data, product race conditions, mocked payment behavior, or environment resets. State the effect Write the effect at the head of the fishbone: 'Upgrade test intermittently misses confirmation banner after payment.' A precise effect keeps the team from drifting into every complaint about the…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in