Supertest is a library that lets you make HTTP requests against your Express application and assert on the response, without starting a server on a fixed port and without writing manual socket code. It extends SuperAgent, an HTTP client, and adds a chainable .expect() method that validates status codes, headers, and body content in a…

Jest and Vitest both provide the same core testing vocabulary—describe, it, expect, mocks, snapshots, and coverage—but they are built on fundamentally different foundations. Jest was created in the CommonJS era and has spent years retrofitting support for ES modules and TypeScript through Babel transforms and experimental flags . Vitest was built from the start on…

The node:test module includes a mocking system built into the runtime. It provides spies, stubs, method replacement, and fake timers without requiring Sinon, Jest, or any other third-party library. The mocking API is exposed through the mock object and through the TestContext object that every test function receives. The distinction between these two entry points…

The Node.js test runner is not a third-party package. It ships with the runtime, stabilized in Node.js 20, and requires no npm install for the core functionality . You write a test file, run node –test, and the runner discovers the file, executes it in a separate child process, and reports the result. The assertion…

Prometheus is a pull-based monitoring system. Unlike agents that push metrics to a central server, Prometheus periodically requests a /metrics endpoint on your application, parses the response, and stores the values as time-series data. This means your Node.js application’s job is not to send metrics anywhere—it is to expose them in a format Prometheus understands,…

A request enters your API, calls a database, invokes a payment service, and returns. Something is slow, but the logs tell you nothing useful—just timestamps and messages from different services with no way to connect them. Distributed tracing solves this by attaching a shared identifier to every operation across every service, so a single request…

Structured logging is the practice of emitting log entries as machine-readable objects—typically JSON—rather than unstructured text. The difference matters at scale. A console.log(“user logged in”) line is readable by a human but nearly useless to a log aggregator that needs to filter by user ID, count errors per endpoint, or correlate entries across services. A…

Running a Node.js process in production with node app.js is a single point of failure. If the process crashes, it stays down. If it consumes too much memory, it takes the server with it. If you need to deploy a new version, you stop the old process and start the new one—creating a window where…