[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-flaky-test::en":3,"gloss-cluster-flaky-test::en":26,"gloss-next-flaky-test::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"flaky-test","dev-tools","Flaky Test","A flaky test is one that passes or fails without any change to the code — green on one run, red on the next. The usual culprits are hidden timing assumptions (a UI test that clicks before the page finished loading), shared state that leaks between tests, reliance on real network calls, or ordering dependencies. Flakiness is corrosive out of proportion to its size: a suite that fails 5% of the time for no reason trains your team to hit \"re-run\" and eventually to ignore red builds entirely — which is exactly when a real regression slips through. For SaaS builders running CI on every pull request, flaky tests directly slow shipping and erode trust in the whole safety net. Treat them as bugs: quarantine the offender so it stops blocking merges, then fix the root cause (add explicit waits, isolate state, mock the network) rather than adding blind retries that just hide the problem.","A flaky test passes or fails with no code change — usually hidden timing assumptions, leaked shared state, real network calls, or order dependence between tests.",null,[11,14,17,20,23],{"slug":12,"name":13},"ci-cd","Continuous Integration \u002F Continuous Deployment (CI\u002FCD)",{"slug":15,"name":16},"code-coverage","Code Coverage",{"slug":18,"name":19},"end-to-end-testing","End-to-End Testing",{"slug":21,"name":22},"regression-testing","Regression Testing",{"slug":24,"name":25},"unit-test","Unit Test",[27,31,34,38,41,44,47,50,53,54,57,60],{"slug":28,"category":5,"name":29,"updated_at":30},"agent","Agent","2026-08-24T02:46:36+00:00",{"slug":32,"category":5,"name":33,"updated_at":30},"ai-code-assistant","AI Coding Assistant",{"slug":35,"category":5,"name":36,"updated_at":37},"api-gateway","API Gateway","2026-08-24T02:46:37+00:00",{"slug":39,"category":5,"name":40,"updated_at":37},"api-versioning","API Versioning",{"slug":42,"category":5,"name":43,"updated_at":30},"autonomous-agent","Autonomous Agent",{"slug":45,"category":5,"name":46,"updated_at":37},"blue-green-deployment","Blue-Green Deployment",{"slug":48,"category":5,"name":49,"updated_at":37},"canary-deployment","Canary Deployment",{"slug":51,"category":5,"name":52,"updated_at":37},"chaos-engineering","Chaos Engineering",{"slug":12,"category":5,"name":13,"updated_at":30},{"slug":55,"category":5,"name":56,"updated_at":37},"circuit-breaker","Circuit Breaker",{"slug":58,"category":5,"name":59,"updated_at":37},"cli","Command-Line Interface (CLI)",{"slug":61,"category":5,"name":62,"updated_at":37},"cloud-development-environment","Cloud Development Environment (CDE)"]