chore: migrate to node.js native test runner #517
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Node.js has added a standard library for Node.js unit testing, which has become more mature over the years, including a test runner, mocking support, coverage, etc.
See: https://nodejs.org/en/learn/test-runner/using-test-runner
I propose we migrate from mocha/sinon/should/nyc to just the standard library, which provides everything we need without adding literally 170 npm dependencies to the project.
node_modulesnot declared inpackage.json)node:test, whereas testing in the Node.js ecosystem has traditionally been very fragmented.All tests have been kept intact, this just migrates from one library to the standard library. I've been using
node:testin all of my other projects as well, and it's pretty great imo.Checklist
Please review this checklist before submitting a pull request.
npm run test:all)