refactor: migrate tests from jest to Node.js test utils#221
Merged
HipsterBrown merged 5 commits intomainfrom Sep 24, 2025
Merged
refactor: migrate tests from jest to Node.js test utils#221HipsterBrown merged 5 commits intomainfrom
HipsterBrown merged 5 commits intomainfrom
Conversation
Owner
Author
|
🚀 PR was released in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To help with upcoming refactors and feature development, I've finally started to add some basic test coverage to this project. It was originally scaffolded with Jest but I never embraced it. Given the existence of Node.js builtin test runner now, I've decided to replace the existing Jest coverage with the Node.js test utils to reduce the number of dependencies in the project and make it easier to integrate.
The "app builder" logic for bringing together all the command modules for the CLI has been split out into
src/app.tsto make it easy to import into a test context without having to spawn a separate process to run the CLI and inspect the output.All new PRs and releases will run these tests along with the existing linter, formatter, and compiler steps in CI.