My test coverage shows different result local vs github #4349
Replies: 2 comments 4 replies
-
Does it differ locally if you use Would be great if you could reduce this into a minimal reproduction. Looking into a complete project is a lot. |
Beta Was this translation helpful? Give feedback.
-
In my case it was a configuration problem:
What i did not know was that cypress and vitest export the lcov.info file to: the .nyc_output/lcov.info file from cypress / nyc is only a temporary file and not the final lcov report. I solved this by cofiguring cypress with a .nycrc file: and vitest with its configuration parameter: |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have integrated vitest with code coverage into my pipeline: https://github.com/mydraft-cc/ui/actions/runs/6603816462/job/17937329518
And I get very different results in github (linux) vs local (windows).
See the following file:
ordering.ts
:In Github:
Local:
What I tried:
node_modules
locallypackage-lock.json
locally.The node versions are almost identical:
Local: v18.17.0
Github: v18.18.2
Beta Was this translation helpful? Give feedback.
All reactions