[{"data":1,"prerenderedAt":74},["ShallowReactive",2],{"term-f\u002Fflaky-test":3,"related-f\u002Fflaky-test":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Ff\u002Fflaky-test.md","Flaky Test",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A flaky test is a test that sometimes passes and sometimes fails for no clear reason — even when nothing changed. It's unreliable, like a friend who sometimes shows up and sometimes doesn't. Flaky tests destroy trust in your test suite because you never know if a failure is real.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A flaky test is a non-deterministic test that produces inconsistent results without code changes. Common causes include timing issues (async\u002Fawait problems), test order dependencies, shared mutable state, random data, and network calls. Flaky tests erode confidence in CI pipelines.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Ignore that failure — it's a known flaky test.\" \u002F \"We have a quarantine suite for flaky tests while we investigate root causes.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"testing","A flaky test is a test that sometimes passes and sometimes fails for no clear reason — even when nothing changed.","intermediate","md","f",{},true,"\u002Fterms\u002Ff\u002Fflaky-test",[49,50,51,52],"End-to-End Test","CI Testing","Test Environment","Regression Test",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Ff\u002Fflaky-test","AjNDVSC8e_C7qDFOrdh409AEJyuOIWAijtFdG7t8KPs",[60,64,68,71],{"title":50,"path":61,"acronym":6,"category":40,"difficulty":62,"description":63},"\u002Fterms\u002Fc\u002Fci-testing","beginner","CI Testing is running all your tests automatically every time someone pushes code.",{"title":49,"path":65,"acronym":66,"category":40,"difficulty":42,"description":67},"\u002Fterms\u002Fe\u002Fend-to-end-test","E2E","An end-to-end test is like hiring a robot to be a user.",{"title":52,"path":69,"acronym":6,"category":40,"difficulty":62,"description":70},"\u002Fterms\u002Fr\u002Fregression-test","A regression test is a test you write AFTER fixing a bug, to make sure that bug never comes back.",{"title":51,"path":72,"acronym":6,"category":40,"difficulty":62,"description":73},"\u002Fterms\u002Ft\u002Ftest-environment","A test environment is a separate version of your app just for running tests.",1776518280388]