[{"data":1,"prerenderedAt":73},["ShallowReactive",2],{"term-t\u002Ftest-environment":3,"related-t\u002Ftest-environment":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\u002Ft\u002Ftest-environment.md","Test Environment",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 test environment is a separate version of your app just for running tests. It has its own database filled with fake data, its own config, and it won't explode real things. You don't run tests against production — that's how you delete real users' data.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A test environment is an isolated infrastructure setup for running automated tests. It includes a separate database, environment variables, and configuration that mirrors production but doesn't affect real data. Tools like Docker Compose make spinning up test environments easy.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Make sure CI runs tests against the test environment, not staging.\" \u002F \"Wipe and reseed the test environment before the integration test run.\"",{"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 test environment is a separate version of your app just for running tests.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Ftest-environment",[49,50,51,52],"CI Testing","Fixture","Integration Test","Flaky Test",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Ft\u002Ftest-environment","tDiSt_608OCrQBLEL0Jq41cVBQ6I9bXk4aGARdMFEhM",[60,63,66,70],{"title":49,"path":61,"acronym":6,"category":40,"difficulty":42,"description":62},"\u002Fterms\u002Fc\u002Fci-testing","CI Testing is running all your tests automatically every time someone pushes code.",{"title":50,"path":64,"acronym":6,"category":40,"difficulty":42,"description":65},"\u002Fterms\u002Ff\u002Ffixture","A fixture is like pre-built test furniture.",{"title":52,"path":67,"acronym":6,"category":40,"difficulty":68,"description":69},"\u002Fterms\u002Ff\u002Fflaky-test","intermediate","A flaky test is a test that sometimes passes and sometimes fails for no clear reason — even when nothing changed.",{"title":51,"path":71,"acronym":6,"category":40,"difficulty":68,"description":72},"\u002Fterms\u002Fi\u002Fintegration-test","If a unit test checks one LEGO brick, an integration test checks that two bricks actually snap together correctly.",1776518318320]