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
bun test --coverage reports coverage percentages for functions and lines like Jest/Vitest/etc, but those also report coverage for statements and branches.
More granular reporting like this is especially helpful to ensure full coverage on terse code like chained ternaries, for example.
What is the problem this feature would solve?
bun test --coverage
reports coverage percentages for functions and lines like Jest/Vitest/etc, but those also report coverage for statements and branches.More granular reporting like this is especially helpful to ensure full coverage on terse code like chained ternaries, for example.
I realize this type of code isn't everyone's cup of tea, but it would be really nice to get the statement and branch coverage numbers from Bun.
What is the feature you are proposing to solve the problem?
Include statement and branch coverage percentages in
bun test --coverage
reports. Something like this in the CLI:I assume this would affect the
lcov
output as well (see #4015).What alternatives have you considered?
Sticking with Jest for now.
The text was updated successfully, but these errors were encountered: