test(coverage): refactor testing structure#5837
Merged
AriPerkkio merged 2 commits intovitest-dev:mainfrom Jun 24, 2024
Merged
Conversation
ba94174 to
2ddccd2
Compare
76b7cd3 to
0599c82
Compare
6 tasks
960f60c to
86a0863
Compare
AriPerkkio
commented
Jun 22, 2024
272b808 to
e943cf4
Compare
e943cf4 to
0fcc708
Compare
6 tasks
Member
Author
|
|
0fcc708 to
3dcef9e
Compare
sheremet-va
approved these changes
Jun 24, 2024
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.
Description
Refactors coverage tests similarly as done for others in #5600. The current coverage tests are a bit of mess.
Most coverage tests will need a way to change coverage options and verify the output. For this we'll need to use Vitest Node APIs. Vitest Workspaces is used to change coverage providers and browser mode. Tests themselves configure different coverage options that are being tested.
Includes fix from #5954 so let's merge that one first.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yamlunless you introduce a new test example.Tests
pnpm test:ci.Documentation
pnpm run docscommand.Changesets
feat:,fix:,perf:,docs:, orchore:.