expressjs / expressjs/discussions

EFI: Using Node.js core testing

Open
#184 21 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
73
Forks
25
PR merge metrics
No merged PRs in 30d

Description

### Motivation

Some testing libraries (and ecosystem) are a lot less maintained that a few years ago, and relying on them can be an issue or a maintenance burden in the coming years. Using the default test runner from Node.js core (part of Node.js 20) would give us a few advantages that ranges from better performances to lower security risks from third party libraries.
Some features may not be available now, so this discussion may be pushed back (or waiting to only keep version that support the Node.js test ecosystem).

### Expectation

Slowly move and use the test runner in all libraries

### Implementation

Update Node.js version
Use test runner ecosystem (test library, assertion, runner, coverage...)

### Status

Part: Technical
Status:
-

### Draft

> Node.js now provides a complete (or almost) test ecosystem, including runners and reporters. Using that part of the stack to replace external dependencies for tests would lower the number of dependencies and reduce the maintenance

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.