4 ms·
seriously, its a function. if you remove the aws/lambda specifics you _should_ have something testable that you then call from your lambda handler.
by crtlaltdel 7y ago
seriously, its a function. if you remove the aws/lambda specifics you _should_ have something testable that you then call from your lambda handler.
- LargeWu 7y agoThat works for unit testing a specific component, but not so well for testing your system end-to-end.
- mypalmike 7y agoThe need for a staging instance for integration testing doesn't disappear when you run your API in lambda.
- 0x445442 7y agoThis! To me the only upside to the whole architecture (from a devs perspective) is that you can deploy these things to production independently of other parts of the system. If you can't do that with confidence because you're attempting to test it's functionality in some larger deployed context you've turned your monolith into a distributed monolith and now you have the worst of both worlds. The good news; you should be able to accomplish most testing locally, in memory. The bad news; your test code is probably going to be much larger and your going to have to be very aware of the data model representing the interface to the lambda and you're going to have to test the different possible states of that data.