express-typescript-skeleton VS supertest

I have been using TsED for a year now and I can say that so far I have not had any problems. It is very comfortable to work with this mini-framework. In addition, the creator provides very fast support and is happy to help with any problems. A few months ago I created a REST API template with hexagonal architecture using TsED.

https://github.com/borjapazr/express-typescript-skeleton

As I say in the README of the project:

This is an opinionated template. The architecture of the code base and the configuration of the different tools used has been based on best practices and personal preferences.

This template does not pretend to have the magic solution to all the problems that a developer may face when creating a REST API using Node.js. This is my contribution, after spending some time on it, to the community. It is an opinionated codebase created based on personal preferences, but also based on the application of best practices.

All criticisms and opinions are welcome, indeed I am very grateful for them. Based on them this could evolve, adapt and become something better. I am sure it will bring something to someone at some point, because even from the worst things something can be learned.

Many thanks to all of you who have taken the time to look at the project.

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