Aim for ~100% coverage; exclude explicitly, ratchet the floor

Test-coverage policy for a project: aim for ~100% coverage of code that carries logic, and treat "when feasible" as a narrow, declared exception — not a licence to skip the hard cases. Use when writing tests, setting or tuning a coverage gate, or deciding whether work is done. Cover every branch and error path of domain/use-case code; exclude only generated/glue/bootstrap code, and exclude it explicitly (annotation / config / pragma) so the gap is declared, never silent. The enforced gate is a floor that only ever ratchets up — a change may not lower coverage. Coverage proves a line ran, not that it was asserted, so pair it with a table-driven oracle. The mechanics (JaCoC…