docker-lambda VS supertest

https://github.com/dherault/serverless-offline https://github.com/lambci/docker-lambda

Step 2: Push a container from your local machine to ECR. Currently, I use sample python lambda docker from https://github.com/lambci/docker-lambda.git

You can see the following projects for some examples of using this plugin to build a layer. They all leverage Docker and the docker-lambda images to compile for AWS’s Lambda environment on any operating system:

I end up using Lambda a lot so lambci is very useful for local testing: https://github.com/lambci/docker-lambda

There are kind souls in this world who created this: https://github.com/lambci/docker-lambda

If all you need is the ability to run a lambda function's code locally you might interested in docker-lambda[1]. I haven't really used localstack or SAM but a couple of years ago when we needed to run some lambda functions locally for development docker-lambda worked well enough.

[1] https://github.com/lambci/docker-lambda

Docker Lambda — Docker Lambda is a tool which tries to replicate the AWS Lambda environment as closely as possible, but within a Docker container. Docker Lambda has support for most of the AWS Lambda run times.

Want to emulate AWS environments? Try docker-lambda.

Supertest is quite popular and easy to use test tool, you can do integration and E2E test as well, you just need to pass it the server instance or a string to make a request and assert over the response.

If the latter, there are a bunch of different options for writing automated tests. One popular way is using Jest to run your tests. If you're trying to test the backend end-to-end flow, you could use Supertest to make requests and assert on the responses.

I did something similar with a full stack Typescript project, using supertest and node-fetch. It was nice.

Unit, Integration and E2E tests using Jest and Supertest

This is why integration tests > unit tests. I really hate mocking and I never bother testing individual units that don't affect how users use my app and code. In your case, I'd just use something like supertest to test this functionality e2e.

Yes, but when every function handler is separate from the router, then you can use node-mocks-http to test each handler, to test the router is simpler to use supertest to write integration tests, for E2E tests I personally recommend [pactum](pactumjs.github.io/)

Simple booking api attempt with Typescript, Express, TypeORM and Postgres. Testing with Jest & Supertest.

In a Node.js application, writing API tests is a good start. They provide more coverage than unit testing. You can use frameworks like Supertest, Jest, or any other library that provides a high-level abstraction for testing APIs.

supertest npm package that helps test HTTP

If you want to write integration tests - https://jestjs.io - https://github.com/visionmedia/supertest