[{"data":1,"prerenderedAt":83},["ShallowReactive",2],{"content-testing-guidance-8-our-guidance":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":12,"contributorPaths":13,"menuType":15,"contentName":16,"slug":17,"readingTime":18,"menu":19,"nextDocItem":76,"previousDocItem":65},"\u003Cp>Serverless developers should favor testing in the cloud as much as possible.\u003C\u002Fp>\n\u003Cp>Tests that run in the cloud provide the most reliable, accurate and complete coverage. Mock frameworks are a valuable tool for writing fast unit tests, especially for testing complex internal business logic. Emulators may be convenient for some use cases but developers should rely on them sparingly.\u003C\u002Fp>\n",{"title":6,"order":7,"callout":8},"Our guidance",8,{"title":9,"description":10,"link":11},"View our code samples","Our open source repository is a great place to begin.  We have serverless test samples in Java, Python, TypeScript and .NET.  Pick a language and navigate to a starter project.","https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fserverless-test-samples","Serverless developers should favor testing in the cloud as much as possible.\n\nTests that run in the cloud provide the most reliable, accurate and complete coverage. Mock frameworks are a valuable tool for writing fast unit tests, especially for testing complex internal business logic. Emulators may be convenient for some use cases but developers should rely on them sparingly.",[14],"content\u002Fcontributors\u002Fdan-fox.json","LIST","Testing your serverless applications","\u002Fcontent\u002Ftesting\u002Fguidance\u002F8-our-guidance","1 min",[20],{"title":21,"content":22},"Testing Guide",[23,30,37,44,51,58,65,72,76],{"title":24,"order":25,"callout":26,"time":18,"path":27,"id":28,"link":29},"Introduction",1,{"title":9,"description":10,"link":11},"1-introduction","1-introduction.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F1-introduction",{"title":31,"order":32,"callout":33,"time":18,"path":34,"id":35,"link":36},"Should you test?",2,{"title":9,"description":10,"link":11},"2-should-you-test","2-should-you-test.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F2-should-you-test",{"title":38,"order":39,"callout":40,"time":18,"path":41,"id":42,"link":43},"Shared responsibility",3,{"title":9,"description":10,"link":11},"3-shared-responsibility","3-shared-responsibility.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F3-shared-responsibility",{"title":45,"order":46,"callout":47,"time":18,"path":48,"id":49,"link":50},"Three Strategies",4,{"title":9,"description":10,"link":11},"4-three-strategies","4-three-strategies.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F4-three-strategies",{"title":52,"order":53,"callout":54,"time":18,"path":55,"id":56,"link":57},"Testing in the Cloud",5,{"title":9,"description":10,"link":11},"5-testing-in-the-cloud","5-testing-in-the-cloud.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F5-testing-in-the-cloud",{"title":59,"order":60,"callout":61,"time":18,"path":62,"id":63,"link":64},"Mocks",6,{"title":9,"description":10,"link":11},"6-mocks","6-mocks.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F6-mocks",{"title":66,"order":67,"callout":68,"time":18,"path":69,"id":70,"link":71},"Emulators",7,{"title":9,"description":10,"link":11},"7-emulators","7-emulators.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F7-emulators",{"title":6,"order":7,"callout":73,"time":18,"path":74,"id":75,"link":17},{"title":9,"description":10,"link":11},"8-our-guidance","8-our-guidance.md",{"title":77,"order":78,"callout":79,"time":18,"path":80,"id":81,"link":82},"Get started with code",9,{"title":9,"description":10,"link":11},"9-get-started","9-get-started.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F9-get-started",1792578874983]