[{"data":1,"prerenderedAt":73},["ShallowReactive",2],{"term-a\u002Farrange-act-assert":3,"related-a\u002Farrange-act-assert":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\u002Fa\u002Farrange-act-assert.md","Arrange Act Assert",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",{},"Arrange Act Assert is just the full name for AAA. You arrange the stage (set up data), act out the scene (call your function), and assert the result (check what happened). Think of it like a play: set, action, review.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Arrange Act Assert is a pattern that structures unit tests into three distinct phases. Arrange sets up test data and preconditions. Act invokes the system under test with those inputs. Assert verifies the outputs or side effects match expectations. It's the foundational structure of clean unit tests.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Every test in this codebase follows Arrange-Act-Assert — keep it consistent.\" \u002F \"The test is too long because the Arrange section is doing too much setup.\"",{"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","Arrange Act Assert is just the full name for AAA.","beginner","md","a",{},true,"\u002Fterms\u002Fa\u002Farrange-act-assert",[49,50,51,52],"AAA Pattern","Given When Then","Test Case","Unit Test",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fa\u002Farrange-act-assert","s170acnmIR9sInrrH0qAhcoo34eGHSzxad6nV83ywVM",[60,64,67,70],{"title":49,"path":61,"acronym":62,"category":40,"difficulty":42,"description":63},"\u002Fterms\u002Fa\u002Faaa-pattern","AAA","AAA stands for Arrange, Act, Assert.",{"title":50,"path":65,"acronym":6,"category":40,"difficulty":42,"description":66},"\u002Fterms\u002Fg\u002Fgiven-when-then","Given When Then is AAA's cousin from the BDD world. Given = the setup situation. When = what the user\u002Fsystem does. Then = what should happen as a result.",{"title":51,"path":68,"acronym":6,"category":40,"difficulty":42,"description":69},"\u002Fterms\u002Ft\u002Ftest-case","A test case is one specific scenario you want to check. 'Does the login work with a correct password?' — that's a test case.",{"title":52,"path":71,"acronym":6,"category":40,"difficulty":42,"description":72},"\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.",1776518256016]