Huge coverage gap between jest and vitest #1240
tqn-treezor
started this conversation in
General
Replies: 2 comments 1 reply
-
(If you see anything unusual that may explain such gap differences, I'm also totally open to suggestions ^^) |
Beta Was this translation helpful? Give feedback.
1 reply
-
I am going to leave that discussion, but for those who come here after me, here are a few things I found out:
Also, all that coverage part is managed by C8 and not Vitest itself - so if you have any issue to report, or any feature request, they should be asked there instead: https://github.com/bcoe/c8 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone! Before I open an issue, I wanted to make sure I wasn't doing anything wrong: I just made the transition from Jest to Vitest, and observed some huge coverage gaps.
In order to try and reduce these, I tried to align my former
jest.config.js
with my newvitest.config.ts
.This is my
jest.config.js
:And this is my
vite.config.ts
:As you can see, my coverages using jest were the following:
When running vitest, I get the following coverages:
The biggest gap observed is with the branches: I jump from 38.04% to 95.96%. Has anyone observed a similar gap?
Beta Was this translation helpful? Give feedback.
All reactions