I wonder if it’s possible to use codecov with the node’s new test runner: Test runner | Node.js v20.7.0 Documentation I’ve tried following: nyc --reporter=lcov node --test --experimental-test-coverage — but nyc doesn’t seem to pick anything. Running just node --test --experimental-test-coverage …

@Elringus as the community boards are soon to be deprecated, I have moved the issue over to our feedback repo to be tracked. Let me know if I’m missing anything.

@Elringus this sounds like an issue with nyc versus Codecov. Can you send a link to a CI run?

Sure: revamp with .net 8 · Elringus/DotNetJS@18e99d4 · GitHub

It looks like node coverage tool produces the report in TAP version 13 format, eg: TAP version 13 # Subtest: boot # Subtest: throws when missing WASM boot resource ok 1 - throws when missing WASM boot resource --- duration_ms: 2.2801 ... # Subtest: throws when missing asse…

I’ve switched to vitest and correct reports are now generated. But codecov still doesn’t see the JavaScript part of the repository. Here is the CI run: revamp with .net 8 · Elringus/DotNetJS@56e6113 · GitHub And here is the codecov page displaying only the C# part of the repository: Codecov Judgi…

Not really, as I’ve switched to vitest; not sure if it’s possible to use codecov with nodejs runner (or rather it’s able to generate a compatible coverge report).

Using with nodejs test runner?

Support

tom October 2, 2023, 5:10pm 6

@Elringus did you resolve your question with a follow-up here? Or are these two things not related?

Topic		Replies	Views
Private repo: There was an error processing coverage reports Support	6	1034	May 21, 2020
Different results when using the node package compared to the bash script	7	256	May 4, 2021
Coverage result not correct for yarn2 monorepo Support	7	482	July 26, 2022
Running codecov cli locally Support	2	2758	June 25, 2023
Sudden and significant drop in coverage Bug Fixes	6	257	April 19, 2023

Using with nodejs test runner?

Related topics