DIFF-COVER(1)

✨ NAME ✨

OK so bestie, meet diff-cover β€” it's the one whose whole job is finding diff lines that need test coverage. πŸ‘‘

It lives in section 1 of the manual (that's User Commands energy, iykyk), so yeah, it's a command you just run. 🫢


🌸 DESCRIPTION 🌸

The usage, verbatim, no notes, no edits, because I would never:

usage: diff-cover [-h] [--html-report HTML_REPORT] [--json-report
JSON_REPORT]
      [--markdown-report MARKDOWN_REPORT] [--format FORMAT]

And what does it do? It automatically finds diff lines that need test coverage. That's it, that's the whole main character arc. It looks at your diff, it looks at your coverage, and it tells you which of those freshly-changed lines are out here living life with zero tests. πŸ˜­πŸ’€

πŸŽ€ options: πŸŽ€

One bullet per flag, exactly as listed, nothing invented, nothing merged, periodt.

  • -h, --help β€” shows this help message and exits. The classic. The little icon. 🌈
  • --html-report HTML_REPORT β€” takes HTML_REPORT as its argument. πŸ’–
  • --json-report JSON_REPORT β€” takes JSON_REPORT as its argument. ✨
  • --markdown-report MARKDOWN_REPORT β€” takes MARKDOWN_REPORT as its argument. πŸ¦‹
  • --format FORMAT β€” takes FORMAT as its argument. 🌸
Lowkey the source material does not describe what those last four actually do, and I am not about to make something up just to sound smart. So if you need the deets, hit that -h, bestie. πŸ™ˆ

Sign-off time, mwah πŸ’…

This gorgeous little page is for diff-cover 10.2.0, and it was born in February 2026. Go forth, cover your diff lines, be the test coverage icon you were always meant to be. πŸŽ€πŸ«Άβ­

πŸ“¦ where this page comes from