supertest VS Docker Compose

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

“Compose simplifies the control of your entire application stack, making it easy to manage services, networks, and volumes in a single, comprehensible YAML configuration file. Then, with a single command, you create and start all the services from your configuration file.” - Docker documentation

curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh # Install docker compose sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose # Apply executable permissions to the binary sudo chmod +x /usr/local/bin/docker-compose # Run Project docker-compose up -d

Docker,

This foundation now opens the door to even more powerful concepts. You can explore more advanced concepts such as container networking, streamlining the management of complex applications with Docker Compose, and how to make your application data persistent using volumes.

In many projects that are containerized, especially in cases where development is also done locally with docker-compose, teams often have two Dockerfiles, 1 for Development, the other for Production. If you happen to have multiple environments like pre-prod, staging and so on, some teams could have different Dockerfiles for these environments.

sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

You can also use Docker Compose to deploy the cluster, without having to write all the previous commands.

[ec2-user]$ sudo yum update -y [ec2-user]$ sudo yum install -y docker [ec2-user]$ sudo service docker start [ec2-user]$ sudo curl -L https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m) -o /usr/local/bin/docker-compose [ec2-user]$ sudo chmod +x /usr/local/bin/docker-compose [ec2-user]$ docker --version Docker version 20.10.23, build 7155243 [ec2-user]$ docker-compose --version Docker Compose version v2.18.1

Docker Compose Documentation

groupadd -g 997 docker gpasswd -a jenkins docker curl -L https://github.com/docker/compose/releases/tag/1.29.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose chmod +x /usr/local/bin/docker-compose #confirm the docker-compose is installed docker-compose version