Open osher opened 2 weeks ago
@bcoe - I'd really appreciate it if you could take a look, or direct me to who can help
Thanks for all the good work! :)
You should use vitest coverage directly instead of c8 + vitest
vitest run --coverage
or c8 + mocha (or node test runner)
c8 + vitest: Some suites get covered other suites ...dont?
I'm working on modernizing and open-sourcing some platform... It's test strategy and test suite is built of two layers:
test/e2e
- end-to-end suites that useschild_process.exec
to run the SUT as cli in multiple scenarios.test/unit
- unit-level suites that add unit-tests to cover specific code-paths which are not covered by any of the e2e scenarios.In the old setup I used
nyc
, but after modernizing it to recent version of node and refactoring fromrequire
toimport
I could not getnyc
to produce coverage for thee2e
suites. Then I found aboutc8
.Astonishingly,
c8
produced coverage for thee2e
right out of the box with zero configuration. However, evidently, I was too fast to rejoice: It does not produce coverage for the unit tests... 🫨The opened codebase is still young and does not take long to install or run - so I hope it can be used as a reproduction scenario...
Reproduction
Clone
https://gitlab.com/prunjs/prun-core
, use branchc8-bug-report
.install (
npm i
)"vanilla" run -
npm -w ecosystem/prun run cover
run only the e2e suites:
npm -w ecosystem/prun run cover -- test/e2e
run only unit tests -
npm -w ecosystem/prun run cover -- test/unit
vitest.config.js
... no coverage is reported for any of the project filesI believe I could do a mish-mash where I ask both tools to produce coverage report in json for the parts it covers successfully, and ask either of the tools to merge them, but that would be a patch. I thought to ask here before I embark on something weird like that...
I hope it's just something silly I'm missing... donno...
🙏 thanks in advance 🙏
fedora in WSL2
, with nodev20.17.0
, npm `v10.8.2'Win11 pro
, with nodev20.12.2
, npmv10.5.0