You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whether this should be fixed by making that merge routine (mentioned in the linked issue) smarter, or making v8toistanbul attempt to get all (including uncovered branches) in the branchMap for a given file, I can't say for sure.
The text was updated successfully, but these errors were encountered:
JustinChristensen
changed the title
Merging multiple converted coverage reports together for the same file results in a mistmatch between the number of properties in branchMap and b.
Merging multiple converted coverage reports together for the same file results in a mismatch between the number of properties in branchMap and b.
Jul 5, 2021
I'm not really sure what the expected behavior here should be. I'm using Playwright to run tests and extract coverage reports from V8 for the same test run, and to then convert and merge them together using a coverage map (from
istanbul-lib-coverage
). .v8-to-istanbul appears to only have branches that were covered in the v8 coverage report in it's
branchMap
. This causes the final merged coverage map to have a mismatch between the number of branches in thebranchMap
and theb
hit counters, because of the way thatFileCoverage
merge is written.Whether this should be fixed by making that merge routine (mentioned in the linked issue) smarter, or making v8toistanbul attempt to get all (including uncovered branches) in the
branchMap
for a given file, I can't say for sure.The text was updated successfully, but these errors were encountered: