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.
Code coverage is a measure of how much of the code is being tested
See: https://www.atlassian.com/continuous-delivery/software-testing/code-coverage
This PR adds the command
npm run test:coverage
to generate a code coverage report after running all unit tests. It achieves this using c8 as per the vitest docshttps://vitest.dev/guide/coverage.html
Currently our code coverage looks like this
![image](https://user-images.githubusercontent.com/8981287/179951484-ac0a4ba3-91d2-42fd-bfbb-e1617be1df32.png)
And we should definitely look to improve this metric going forward