BISECT-PPX-REPORT(1)

πŸ’– BISECT-PPX-REPORT πŸ’–

okay bestie, gather round, because we're talking about bisect-ppx-report, and she is that girl. Fr fr, this is the tool that makes coverage reports for OCaml and Reason. Like, it looks at your code, tells you what your tests actually touched, and makes it all pretty. Main character energy, no cap. ✨


🌸 NAME 🌸

bisect-ppx-report β€” generate coverage reports for OCaml and Reason. periodt. πŸ’…


πŸŽ€ DESCRIPTION πŸŽ€

BISECT-PPX-REPORT(1) β€” the Bisect-ppx-report Manual, and yes, the manual is out here citing itself, she's self-aware, we love that for her. πŸ’–

πŸ“– NAME

bisect-ppx-report β€” generate coverage reports for OCaml and Reason. (Yes, it says it twice. Iconic behaviour. She knows her name and she's not shy about it.) πŸ‘‘

πŸ¦‹ SYNOPSIS

bisect-ppx-report COMMAND ...

That's the whole vibe: you pick a COMMAND, she does the thing.

✨ USAGE EXAMPLE

bisect-ppx-report html
bisect-ppx-report send-to Coveralls
bisect-ppx-report summary

And listen β€” for the full 411 on any individual command, including all her options, just run bisect-ppx-report COMMAND --help. Go on, she loves being asked. 🫢

πŸ’… COMMANDS

Pick your fighter:

  • cobertura [--coverage-path=DIRECTORY] [--ignore-missing-files] [--source-path=DIRECTORY] [OPTION]... OUTPUT_FILE [COVERAGE_FILES]... Generate a Cobertura XML report. Very XML. Very official. ⭐
  • coveralls [OPTION]... OUTPUT_FILE [COVERAGE_FILES]... Generate a Coveralls JSON report β€” this one's for when you wanna hook up with web services manually, iykyk. 🌈
  • html [OPTION]... [COVERAGE_FILES]... Generate an HTML report, locally, right there on your machine. Cute, self-contained, no internet drama. πŸ’–
  • merge [--coverage-path=DIRECTORY] [OPTION]... OUTPUT_FILE [COVERAGE_FILES]... Merge coverage files together. Friendship bracelet behaviour β€” everybody gets combined. 🫢
  • send-to [OPTION]... SERVICE [COVERAGE_FILES]... Send the report off to a supported web service. She's posting it. πŸ“€
  • summary [--coverage-path=DIRECTORY] [--per-file] [OPTION]... [COVERAGE_FILES]... Write a coverage summary to STDOUT. Just the highlights, bestie. No fluff. ✨

βš™οΈ COMMON OPTIONS

  • --help[=_FMT_] (default=auto) β€” Show this help in format _FMT_. The value _FMT_ must be one of auto, pager, groff or plain. With auto, the format is pager or plain whenever the TERM env var is dumb or undefined. (Shoutout to TERM for taking one for the team.) 🌸

πŸšͺ EXIT STATUS πŸšͺ

bisect-ppx-report exits with:

  1. 0 β€” on success. ate. πŸ’…
  2. 1 β€” on error. 😭
  3. 123 β€” on indiscriminate errors reported on standard error.
  4. 124 β€” on command line parsing errors.
  5. 125 β€” on unexpected internal errors (bugs). πŸ’€ (that one's a bug, she said it herself, do not come for her)

Bisect-ppx-report β€” BISECT-PPX-REPORT(1). πŸŽ€


πŸ‘€ SEE ALSO πŸ‘€

The full documentation for bisect-ppx-report is maintained as a Texinfo manual. If the info and bisect-ppx-report programs are properly installed at your site, the command

info bisect-ppx-report

should give you access to the complete manual. Like, that's the whole lore drop. Go read it. 🧚


okay that's the whole page bestie, you're so welcome πŸ’œ this lil masterpiece is from bisect-ppx-report 2.8.3+dfsg, dated July 2026 β€” yes, the future, she's early, she's always early. slay ✨

πŸ“¦ where this page comes from