From: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
To: John Christopher McAlpine <jmcalpin@nmt.edu>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Use of unit testing frameworks in OCaml
Date: Thu, 10 Sep 2015 12:09:36 +0200 [thread overview]
Message-ID: <CAHvkLrNkdC04S3h227n+8gKidmca5veLatdaWQP5zUCm9rHpTg@mail.gmail.com> (raw)
In-Reply-To: <55F09806.1030507@nmt.edu>
One reason to avoid OCaml tests framworks for the compiler is probably
that, if the compiler is broken, we still want to be able to run the
testsuite, to break down the problem to the smallest failing test. If
the test framework is written in OCaml and compiled by the failing
compiler, it might not be able to run the tests at all. Maybe a
solution would be to use a tests framework written for OCaml... but in
another language :-) (which is currently the case, it is written in
Makefiles...)
--Fabrice
On Wed, Sep 9, 2015 at 10:35 PM, John Christopher McAlpine
<jmcalpin@nmt.edu> wrote:
> From what I can tell, the tests for the OCaml compiler and standard
> libraries are all done with a fairly small framework designed specifically
> for testing the compiler and standard libraries. Is there any particular
> reason not to use a tool such as OUnit or Broken for these tests? I am aware
> that adding dependencies to the compiler is generally frowned upon, but
> these libraries could significantly improve the maintainability of the core
> language and libraries.
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
--
Fabrice LE FESSANT
Chercheur en Informatique
INRIA Paris Rocquencourt -- OCamlPro
Programming Languages and Distributed Systems
prev parent reply other threads:[~2015-09-10 10:09 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
2015-09-09 23:18 ` Gerd Stolpmann
2015-09-10 10:09 ` Fabrice Le Fessant [this message]
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=CAHvkLrNkdC04S3h227n+8gKidmca5veLatdaWQP5zUCm9rHpTg@mail.gmail.com \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@inria.fr \
--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