[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"term-t\u002Ftest-pyramid":3,"related-t\u002Ftest-pyramid":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-pyramid.md","Test Pyramid",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",{},"The Test Pyramid is a strategy for how many of each test type to have. Many fast unit tests at the bottom (the base), fewer integration tests in the middle, and just a handful of slow E2E tests at the top. Like a pyramid — wide base, narrow top. Invert it and you have a slow, expensive disaster.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"The Test Pyramid (coined by Mike Cohn) recommends having many unit tests, fewer integration tests, and even fewer end-to-end tests. Unit tests are fast and cheap; E2E tests are slow and expensive. An inverted pyramid (mostly E2E) leads to slow, brittle test suites.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Our test suite is an inverted pyramid — too many E2E tests and almost no unit tests.\" \u002F \"Follow the test pyramid: write 10 unit tests for every integration test.\"",{"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","The Test Pyramid is a strategy for how many of each test type to have.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Ftest-pyramid",[49,50,51,52,53],"Unit Test","Integration Test","End-to-End Test","Smoke Test","CI Testing",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Ftest-pyramid","2vEhlxrjkXqrK5yRZqFzHGQ3uF9x0yYF4lzTuPWN83s",[61,64,69,72,75],{"title":53,"path":62,"acronym":6,"category":40,"difficulty":42,"description":63},"\u002Fterms\u002Fc\u002Fci-testing","CI Testing is running all your tests automatically every time someone pushes code.",{"title":51,"path":65,"acronym":66,"category":40,"difficulty":67,"description":68},"\u002Fterms\u002Fe\u002Fend-to-end-test","E2E","intermediate","An end-to-end test is like hiring a robot to be a user.",{"title":50,"path":70,"acronym":6,"category":40,"difficulty":67,"description":71},"\u002Fterms\u002Fi\u002Fintegration-test","If a unit test checks one LEGO brick, an integration test checks that two bricks actually snap together correctly.",{"title":52,"path":73,"acronym":6,"category":40,"difficulty":42,"description":74},"\u002Fterms\u002Fs\u002Fsmoke-test","A smoke test is the most basic sanity check: does the app even start? Does it not immediately crash?",{"title":49,"path":76,"acronym":6,"category":40,"difficulty":42,"description":77},"\u002Fterms\u002Fu\u002Funit-test","A unit test is like checking that one single LEGO brick isn't broken before you use it in your big castle.",1776518318412]