pino VS supertest

Fastify comes with Pino by default, but logging must be enabled for it to work:

Learn more about logging in Fastify and how to customize the Pino logger.

The Fastify framework includes the Pino logger by default (a really great logger with lots of cool features that doesn't compromise on performance). The framework itself allows a lot of really cool stuff, like controlling the level of logs at runtime.

Fastify provides a built-in logging mechanism based on Pino that allows you to capture various events in your applications. Once enabled, Fastify logs all incoming requests to the server and errors that occur while processing said requests. It also provides a convenient way to log custom messages through the log() method on the Fastify instance or the request object.

1. pino

Have a look at https://github.com/pinojs/pino

NodeJS -> Pino, Winston, Bunyan, Npmlog, e.t.c.

Using pino as a logger, for every request on the _server_ , a unique ID generated client side in the headers, so a log may be something like:

pino (logger)

Pino is also a popular Node.js logging library alternative for developers. There are claims that it is 5x faster than other Node.js logging libraries besides providing standard features such as the ability to choose a storage medium, log levels, and formatting capabilities. Pino is also highly extensible, flexible, and easy to integrate with Node.js frameworks such as Express, Fastify, and Restify. The library is a low-overhead Node.js logging library and supports asynchronous logging despite being fast. Pino also gives you the ability to create child loggers.

Here in the issue you can see how people struggle with setting a header, it's objectively harder to make handy functions on top of supertest to perform authorized requests.

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.

Unit, Integration and E2E tests using Jest and Supertest

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

SuperTest is helpful for testing the GraphQL endpoints. We can use it to send HTTP requests and make assertions on the responses. If you are working on a Fastify project, as we will see, you use inbuilt Fastify functionality and don't need to add supertest.