Use coverage to find untested risk, not as a quota that rewards assertion-free tests.
Chasing a coverage number produces tests that execute code without verifying behavior.
BeforeMerge scans your pull requests against this rule and dozens more. Get actionable feedback before code ships.
Coverage measures which lines ran, not whether behavior is correct. Mandating a percentage incentivizes tests that touch code without asserting anything. Use coverage to spot untested risk, and judge tests by the behaviors they protect.
// Bad — runs code, asserts nothing (inflates coverage)
it("covers process", () => { process(input); });
// Good — covers and verifies behavior
it("flags invalid input", () => expect(process(bad).valid).toBe(false));