From: Anton Bachin <antonbachin@yahoo.com>
To: caml-list@inria.fr
Subject: [Caml-list] [ANN] Bisect_ppx 1.0.0 – Modernized code coverage for OCaml
Date: Wed, 10 Feb 2016 09:33:17 -0600 [thread overview]
Message-ID: <1FE0ECD4-BBD6-48DA-95BD-BB240E07484C@yahoo.com> (raw)
Hello,
We would like to announce the release of Bisect_ppx 1.0.0, a code coverage tool
for OCaml with appealing reports:
https://github.com/rleonid/bisect_ppx
You can see a live coverage report here:
http://rleonid.github.io/bisect_ppx/coverage/
Reports can also be submitted to Coveralls.io using ocveralls [1]. See an
example here [2].
Bisect_ppx is a fork of the original Bisect by Xavier Clerc, with extensive
further development. Differences from Bisect, and from earlier versions of
Bisect_ppx, include:
- the nicer and more legible HTML reports,
- more thorough instrumentation, now including nested functions and or-patterns,
- improved compatibility with other PPX rewriters,
- an Ocamlbuild plugin,
- many bugfixes, and
- usage, performance, and documentation improvements.
Bisect_ppx was originally forked to update and maintain Bisect's PPX mode, with
the OCaml community moving to PPX. Bisect_ppx does not have Bisect's Camlp4
dependency. We do not believe that the original Bisect is being actively
maintained.
Regards,
Anton & Leonid
P.S. If you are working on a project that uses Bisect_ppx, please let us know!
[1]: https://github.com/sagotch/ocveralls
[2]: https://coveralls.io/builds/4913198/source?filename=src%2Fsyntax%2FinstrumentPpx.ml
next reply other threads:[~2016-02-10 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 15:33 Anton Bachin [this message]
2016-02-10 16:46 ` David MENTRE
2016-02-10 19:27 ` Anton Bachin
2016-02-12 6:44 ` David MENTRÉ
2016-02-12 9:18 ` Anton Bachin
2016-02-10 19:00 ` Gerd Stolpmann
2016-02-10 19:23 ` Gabriel Scherer
2016-02-10 19:33 ` Anton Bachin
2016-02-10 21:48 ` Gerd Stolpmann
2016-02-10 21:49 ` Alain Frisch
2016-02-11 1:16 ` Anton Bachin
2016-02-11 10:42 ` Gerd Stolpmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1FE0ECD4-BBD6-48DA-95BD-BB240E07484C@yahoo.com \
--to=antonbachin@yahoo.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox