Hello all, any recommendations for reference that expands the testing page of the guide? I was hoping for neat SSTesque ways to 1. test lambdas that use AWS resources (e.g. unit test CRUD persistence) 2. test end-points (e.g. integration test CRUD persistence)

I use JEST for both. Unit tests mock out everything to test only the compilation unit (module, in Javascript). Integration tests are separate; they populate test data in the cloud and use the APIs via node-fetch.

Thanks. The pointers are useful, I can imagine what it might take.

I’ve seen many teams follow the PR workflow, ie. 1 stage per PR. You can use jest, cypress, whatever u r familiar with to run tests against it.

Thanks. Reading the best practices section got me to a similar place, where it says –

You want to configure your CI/CD pipeline to automatically bring these stages up, test against them, and tear them down once you are done.

So good to see that seed has that built-in.

Would be nice if we could run unit tests for other languages inside SEED. I use Golang lambdas and Typescript CDK. Currently a Makefile inside a Github action but would prefer to use SEED

@Toby Harris yeah it’s an area we are thinking a lot about this and have some plans to improve the testing experience for SST. Actually just chatted w/ @thdxr about this earlier today.

@Frank Yes. Take the most vanilla Lambda, say https://serverless-stack.com/chapters/add-an-api-to-get-a-note.html, and the guide doesn’t actually give any path to test it. In the monolithic back-end work I’ve done before, there’s lots of calling the route handlers and then inspecting the db. For handlers that use remote APIs, I see the general trend of mocking. But a) it strikes me that the automation of SST deploy means mocking is less necessary and b) there’s no pointer either way in the guide. It’s an untested API, pretty much.