test: add front-end coverage reporting #2738
Open
Conversation
This file contains 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.
Nearly all of this PR's diff is package-lock.json noise.
This PR enables front-end test coverage reporting, both in the terminal and via the Vitest official dashboard:
How to test this PR:
sail npm installsail npm run test:coverageThis should cause tests to begin running and a tiny Vitest service to start at http://localhost:51204/__vitest__/.
Manually navigate your browser to http://localhost:51204/__vitest__/.
If
npm run test:coverageis run without Sail, the browser window automatically pops. Needing to do manual navigation is a Sail limitation.After tests are done running, coverage should also appear in the terminal itself. If you navigate to the URL above, you can click a button to view coverage: