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.
This PR adds unit and integration tests using Jest.
Description
I've been playing around with this for a little while as a way of getting to grips with Jest, and feel like I've finally gotten to a point where it's worth sharing and discussing.
The solution I've landed on seems to work well. I've created some tests in the
utils
directory for each function in there, as well as a larger integration test in the root which is able to run various commands from the CLI and adjusts the mocked filesystem to emulate different outcomes.To be perfectly honest I didn't realise there were tests running during CI already until I came to write this PR, but it feels like there's some value in this approach so hopefully it's beneficial.
Change log
package
variable name topkg
to avoid issue withpackage
being a reserved keyword which was flagged in Jest - docsSample test output