From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: John Christopher McAlpine <jmcalpin@nmt.edu>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Use of unit testing frameworks in OCaml
Date: Thu, 10 Sep 2015 11:22:59 +0200 [thread overview]
Message-ID: <m24mj2zkzw.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <CAPFanBG=FDN-7Mm+Or6sdxWFpem4MWK-gy8C7BEQDu7g0QYAHw@mail.gmail.com> (Gabriel Scherer's message of "Wed, 9 Sep 2015 23:29:27 +0200")
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
Hi Gabriel,
On 2015-09-09 23:29, Gabriel Scherer <gabriel.scherer@gmail.com> writes:
> - A way to collect coverage checking information (which parts of the
> compiler codebase are exercized by the tests?). I started working on
> it once by just adding Bisect somewhere in the compiler build system,
> but lost motivation before getting into a a work-out-of-the-box state
> (it generated many independent coverage files, one for each test, that
> would have to be aggregated). I think that should not be too hard.
We use bisect to test coverage of the JavaScript test suite on our
interpreter, and aggregating the results is simply a matter of doing
bisect-report -html report bisect*.out
(assuming you want to put the generated report in the report directory).
Best,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Last week athmospheric CO₂ average (Updated September 6, 2015, Mauna Loa Obs.):
377.86 ppm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-09-10 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 20:35 John Christopher McAlpine
2015-09-09 20:55 ` Sébastien Hinderer
2015-09-09 22:29 ` John Christopher McAlpine
2015-09-09 23:32 ` Daniel Bünzli
2015-09-09 23:36 ` Raoul Duke
2015-09-09 23:53 ` Hendrik Boom
2015-09-09 21:29 ` Gabriel Scherer
2015-09-10 9:22 ` Alan Schmitt [this message]
2015-09-09 23:18 ` Gerd Stolpmann
2015-09-10 10:09 ` Fabrice Le Fessant
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=m24mj2zkzw.fsf@charm-ecran.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=jmcalpin@nmt.edu \
/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