bun test --coverage results in non-zero exit code when coverage falls below default level

[jakeboone02]

What version of Bun is running?

0.7.3

What platform is your computer?

Darwin 22.6.0 x86_64 i386

What steps can reproduce the bug?

Run bun test --coverage in a project with no bunfig.toml and where the coverage is < 90%.

What is the expected behavior?

Without coverageThreshold explicitly configured by the user, --coverage should simply report coverage and not force a non-zero exit code. Non-zero exit codes should only appear for passing test suites if coverageThreshold is explicitly configured.

What do you see instead?

--coverage results in a non-zero exit code when coverage falls below coverageThreshold, even if it falls back to the default of 90%.

Additional information

The requested change is to match the behavior of Jest. (I haven't tried Vitest.)

• Passing tests + no threshold configured + coverage < default = zero exit code.
• Passing tests + threshold configured + coverage < threshold = non-zero exit code.