From: Jeremie Dimino <jdimino@janestreet.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>,
"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml projects with tests
Date: Thu, 8 Oct 2015 10:18:05 +0100 [thread overview]
Message-ID: <CANhEzE6QHAqzTeSY1Kidrjez9YdTpD=fC5G0gVGb8cQWoNjhOA@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBGThN4FrEm3s4AvV7L-i5d9df7zHJ1zTgWzgh7S9Hf8Fw@mail.gmail.com>
On Thu, Oct 8, 2015 at 9:21 AM, Gabriel Scherer
<gabriel.scherer@gmail.com> wrote:
> Other projects have their own preprocessing tools to manipulate tests. I
> don't have exhaustive knowledge of what is out there, but there is Jun
> Furuse's ppx_test (on top of the oUnit library). there is pa_ounit (
> https://github.com/janestreet/pa_ounit ), and Janestreet also has pa_test
> and a PPX successor (also named ppx-test, I would guess). pa_ounit is the
> best documented of these projects, as it describes the execution model.
For the pointers:
- the ppx replacement of pa_ounit is ppx_inline_test [1]. We dropped
the "ounit" as it's not using ounit at all
- the ppx replacement of pa_test is ppx_assert [2]. ppx_test was
already taked and was a bit too generic anyway
[1] https://github.com/janestreet/ppx_inline_test
[2] https://github.com/janestreet/ppx_assert
--
Jeremie
next prev parent reply other threads:[~2015-10-08 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 7:43 Sébastien Hinderer
2015-10-08 8:10 ` Francois Berenger
2015-10-08 8:21 ` Gabriel Scherer
2015-10-08 8:34 ` Hendrik Boom
2015-10-08 9:18 ` Jeremie Dimino [this message]
2015-10-08 8:26 ` Hendrik Boom
2015-10-08 15:04 ` Leonid Rozenberg
2015-10-08 15:56 ` Thomas Gazagnaire
2015-10-09 12:29 ` Richard W.M. Jones
2015-10-09 12:37 ` Richard W.M. Jones
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='CANhEzE6QHAqzTeSY1Kidrjez9YdTpD=fC5G0gVGb8cQWoNjhOA@mail.gmail.com' \
--to=jdimino@janestreet.com \
--cc=Sebastien.Hinderer@inria.fr \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).