[{"data":1,"prerenderedAt":80},["ShallowReactive",2],{"term-t\u002Ftest-impact-analysis":3,"related-t\u002Ftest-impact-analysis":60},{"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":54,"sitemap":55,"stem":58,"subcategory":6,"__hash__":59},"terms\u002Fterms\u002Ft\u002Ftest-impact-analysis.md","Test Impact Analysis",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",{},"Test impact analysis is your CI pipeline being smart enough to ask which tests could this change have actually broken, instead of blindly rerunning your entire test suite for a one-line comment tweak. It traces which code paths each test touches, so a small change only reruns the tests that could plausibly care, and your fifteen minute suite turns into ninety seconds.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Test impact analysis maps the dependency graph between test cases and the code paths they exercise, then uses that map to select only the tests affected by a given change instead of running the full suite. It's commonly built on code coverage data collected from previous runs and is a core feature of tools like Microsoft's TIA, Bazel's test selection, and Nx's affected commands.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Test impact analysis cut our PR pipeline from 20 minutes to 3.\" \u002F \"Don't trust test impact analysis blindly on flaky infra, it can miss indirect dependencies.\"",{"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","Test impact analysis is your CI pipeline being smart enough to ask which tests could this change have actually broken, instead of blindly rerunning your en...","advanced","md","t",{},true,"\u002Fterms\u002Ft\u002Ftest-impact-analysis",[49,50,51,52,53],"Test Suite","CI Testing","Coverage","Nx","Monorepo Tools",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Ftest-impact-analysis","Mn5PnT2FxN8BhZGHGeMdj742mzyvW0wuZL37wnybZpM",[61,65,68,73,77],{"title":50,"path":62,"acronym":6,"category":40,"difficulty":63,"description":64},"\u002Fterms\u002Fc\u002Fci-testing","beginner","CI Testing is running all your tests automatically every time someone pushes code.",{"title":51,"path":66,"acronym":6,"category":40,"difficulty":63,"description":67},"\u002Fterms\u002Fc\u002Fcoverage","Coverage tells you what percentage of your code is actually tested. 80% coverage means 80% of your lines are touched by at least one test.",{"title":53,"path":69,"acronym":6,"category":70,"difficulty":71,"description":72},"\u002Fterms\u002Fm\u002Fmonorepo-tools","cicd","intermediate","Monorepo tools help you manage a massive codebase where everything — frontend, backend, shared libraries — lives in one repository without losing your mind",{"title":52,"path":74,"acronym":6,"category":75,"difficulty":71,"description":76},"\u002Fterms\u002Fn\u002Fnx","general","Nx is like a smart contractor for your monorepo.",{"title":49,"path":78,"acronym":6,"category":40,"difficulty":63,"description":79},"\u002Fterms\u002Ft\u002Ftest-suite","A test suite is just a collection of related tests grouped together.",1792528130111]