···
3
+
synopsis: "Code coverage for OCaml"
5
+
homepage: "https://github.com/aantron/bisect_ppx"
6
+
doc: "https://github.com/aantron/bisect_ppx"
7
+
bug-reports: "https://github.com/aantron/bisect_ppx/issues"
9
+
dev-repo: "git+https://github.com/aantron/bisect_ppx.git"
11
+
"Xavier Clerc <bisect@x9c.fr>"
12
+
"Leonid Rozenberg <leonidr@gmail.com>"
13
+
"Anton Bachin <antonbachin@yahoo.com>"
16
+
"Anton Bachin <antonbachin@yahoo.com>"
17
+
"Leonid Rozenberg <leonidr@gmail.com>"
22
+
"cmdliner" {>= "1.0.0"}
24
+
"ocaml" {>= "4.03.0"}
25
+
"ppxlib" {>= "0.28.0"}
27
+
"dune" {with-test & >= "3.0.0"}
28
+
"ocamlformat" {with-test & = "0.16.0"}
32
+
["dune" "build" "-p" name "-j" jobs]
33
+
["dune" "build" "-p" name "-j" jobs "@compatible"] {with-test}
36
+
description: "Bisect_ppx helps you test thoroughly. It is a small preprocessor
37
+
that inserts instrumentation at places in your code, such as if-then-else and
38
+
match expressions. After you run tests, Bisect_ppx gives a nice HTML report
39
+
showing which places were visited and which were missed.
41
+
Usage is simple - add package bisect_ppx when building tests, run your tests,
42
+
then run the Bisect_ppx report tool on the generated visitation files."
45
+
src: "https://github.com/aantron/bisect_ppx/archive/2.8.3.tar.gz"
46
+
checksum: "md5=8c755c13e8d90f665986d842a41669f5"