chore: vitest project config #32447
Merged
chore: vitest project config #32447
Conversation
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
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
cypress
|
||||||||||||||||||||||||||||
| Project |
cypress
|
| Branch Review |
chore/vitest-project-config
|
| Run status |
|
| Run duration | 10m 00s |
| Commit |
|
| Committer | Cacie Prins |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
0
|
Pending
|
694
|
Skipped
|
0
|
Passing
|
130
|
| View all changes introduced in this branch ↗︎ | |
cacieprins
commented
Sep 8, 2025
cacieprins
commented
Sep 8, 2025
cacieprins
commented
Sep 8, 2025
cacieprins
commented
Sep 8, 2025
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
AtofStryker
approved these changes
Sep 9, 2025
| 'cli/vitest.config.*', | ||
| ], | ||
| exclude: ['**/node_modules/**', '**/dist/**', 'system-tests/**'], | ||
| coverage: { |
There was a problem hiding this comment.
where exactly does the coverage get output to and do we need to check if they are generated similar to our current CI process?
There was a problem hiding this comment.
They aren't, yet! I've been using it personally to check coverage locally, but not anything in CI.
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.
Additional details
Some vitest extensions have a pretty hard time in a monorepo with multiple vitest configs.
This project config is set up to quiet those warnings. It's not super useful to run vitest from root at this point - it takes quite some time, partially because some of our vitest suites are more integration tests than unit tests (particularly in
npm/cypress-schematic).Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation?type definitions?