-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@vitest/coverage-istanbul runs excluded files #6058
Comments
@AriPerkkio Do you have any ideas on how to fix this issue? Thanks! |
Hello @MKhasib. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with |
The (partial) configuration shown in description is enough to solve this. Only |
What's |
@AriPerkkio Thanks for the quick response, I tried creating a reproducible repo but it seemed vitest included in coverage is working as expected just in the new repo. I am investigating why it doesn't on the private repo(actually it does exclude some files but not all .vue files from coverage) I will close this issue for now, thank you soo much for the help! |
Describe the bug
I am migrating from jest to vitest in a private repo where I used the following config
However, coverage-istanbul instrument picks up vue files used inside the
.js
test files and adds it to the total coverage reportIs there a way to exclude all vue files used inside .js tests from getting into the final coverage report?
Reproduction
import any .vue file inside a test .js file
System Info
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: