In the first part of this two-part series, we'll look at the main capabilities of the Node.js test runner.

AppSignal's platform is a resource for developers and DevOps teams, offering insights into application monitoring, error tracking, and performance optimization. Through articles, tutorials, and case studies, AppSignal offers insights into identifying and resolving performance issues in web applications. Developers can learn about monitoring key metrics, tracking errors, and optimizing code to deliver fast and reliable user experiences.

AppSignal

Node.js has introduced a stable test runner in its standard library starting from version 18. This inclusion aims to emphasize the importance of testing as an integral part of development and to provide core tooling out-of-the-box, addressing the minimalist philosophy traditionally held by Node.js. The post walks through the core capabilities of the test runner, from writing and executing tests to organizing and customizing them. It also demonstrates the usage through examples, showing how to write unit tests, run them, handle test failures, and organize test cases.

Exploring the Node.js Native Test Runner

Why Was A Test Runner Added to Node.js 18+?

<p>nice to know, every 3rd party lib that can be avoided should</p>
