From: "Richard W.M. Jones" <rich@annexia.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml projects with tests
Date: Fri, 9 Oct 2015 13:29:17 +0100 [thread overview]
Message-ID: <20151009122917.GF20503@annexia.org> (raw)
In-Reply-To: <20151008074315.GA1466@pl-59055.rocqadm.inria.fr>
On Thu, Oct 08, 2015 at 09:43:15AM +0200, Sébastien Hinderer wrote:
> Dear all,
>
> Recently the topic was discussed here and several testing frameworks were
> mentionned.
>
> I am wondering whether there are well established projects that actually
> use tests (unit tests and others) and that could be used as sources of
> inspiration?
libguestfs tools have extensive tests.
We have a few unit tests, using OUnit2. An example:
https://github.com/libguestfs/libguestfs/blob/master/v2v/v2v_unit_tests.ml
But the vast majority of the upstream tests use automake's (terrible)
test framework, eg:
https://github.com/libguestfs/libguestfs/blob/master/v2v/Makefile.am#L239
https://github.com/libguestfs/libguestfs/blob/master/builder/Makefile.am#L224
https://github.com/libguestfs/libguestfs/blob/master/resize/Makefile.am#L130
We also have external tests that are non-free so can't be distributed
with the upstream sources:
http://git.annexia.org/?p=virt-v2v-test-cases-nonfree.git;a=summary
We also have a public CI system:
https://ci.centos.org/view/libguestfs/
And finally, we use some proprietary software called Polarion to track
a massive set of tests (many run manually) that control what gets into RHEL.
Those tests aren't published at all.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2015-10-09 12:29 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
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 [this message]
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=20151009122917.GF20503@annexia.org \
--to=rich@annexia.org \
--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;
as well as URLs for NNTP newsgroup(s).