[{"data":1,"prerenderedAt":83},["ShallowReactive",2],{"content-testing-guidance-4-three-strategies":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":12,"contributorPaths":13,"menuType":15,"contentName":16,"slug":17,"readingTime":18,"menu":19,"nextDocItem":48,"previousDocItem":37},"\u003Cp>This guide focuses on three key strategies for writing automated tests for cloud-native applications: emulators, mocks, and testing in the cloud. These are the most common techniques used by serverless application developers.\u003C\u002Fp>\n\u003Cp>Emulators are desktop applications that resemble services in the cloud. Mocks are replacement objects that may simulate the behavior of cloud services for unit tests. Testing in the cloud is the technique of writing tests that run against architecture components that are previously deployed into the context of the cloud.\u003C\u002Fp>\n\u003Cp>Well-designed serverless applications may employ a variety of these techniques to satisfy a range of requirements and conditions. However, we recommend developers focus on testing in the cloud as much as possible.\u003C\u002Fp>\n\u003Cp>Want to see code samples for these three techniques? Check out \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fserverless-test-samples\">this GitHub repository\u003C\u002Fa>. \u003C\u002Fp>\n",{"title":6,"order":7,"callout":8},"Three Strategies",4,{"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","This guide focuses on three key strategies for writing automated tests for cloud-native applications: emulators, mocks, and testing in the cloud. These are the most common techniques used by serverless application developers.\n\nEmulators are desktop applications that resemble services in the cloud. Mocks are replacement objects that may simulate the behavior of cloud services for unit tests. Testing in the cloud is the technique of writing tests that run against architecture components that are previously deployed into the context of the cloud.\n\nWell-designed serverless applications may employ a variety of these techniques to satisfy a range of requirements and conditions. However, we recommend developers focus on testing in the cloud as much as possible.\n\nWant to see code samples for these three techniques? Check out [this GitHub repository](https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fserverless-test-samples). \n\n",[14],"content\u002Fcontributors\u002Fdan-fox.json","LIST","Testing your serverless applications","\u002Fcontent\u002Ftesting\u002Fguidance\u002F4-three-strategies","1 min",[20],{"title":21,"content":22},"Testing Guide",[23,30,37,44,48,55,62,69,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":6,"order":7,"callout":45,"time":18,"path":46,"id":47,"link":17},{"title":9,"description":10,"link":11},"4-three-strategies","4-three-strategies.md",{"title":49,"order":50,"callout":51,"time":18,"path":52,"id":53,"link":54},"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":56,"order":57,"callout":58,"time":18,"path":59,"id":60,"link":61},"Mocks",6,{"title":9,"description":10,"link":11},"6-mocks","6-mocks.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F6-mocks",{"title":63,"order":64,"callout":65,"time":18,"path":66,"id":67,"link":68},"Emulators",7,{"title":9,"description":10,"link":11},"7-emulators","7-emulators.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F7-emulators",{"title":70,"order":71,"callout":72,"time":18,"path":73,"id":74,"link":75},"Our guidance",8,{"title":9,"description":10,"link":11},"8-our-guidance","8-our-guidance.md","\u002Fcontent\u002Ftesting\u002Fguidance\u002F8-our-guidance",{"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",1792578874952]