From: Yaron Minsky <yminsky@janestreet.com>
To: Simon Cruanes <simon.cruanes.2007@m4x.org>
Cc: "Török Edwin" <edwin+ml-ocaml@etorok.net>,
"caml-list@inria.fr" <caml-list@inria.fr>,
"Carl Eastlund" <ceastlund@janestreet.com>
Subject: Re: [Caml-list] Quick Check like testing for OCaml?
Date: Tue, 15 Sep 2015 09:09:00 -0400 [thread overview]
Message-ID: <CACLX4jR2W+Q2--O+YPBYM8k0tSBES9JxRDVfju9y1QR3D89OTg@mail.gmail.com> (raw)
In-Reply-To: <20150913155224.GE16946@carty>
[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]
Core_kernel has a recently added quickcheck library. Carl Eastlund, who is
the main author, is finishing up a blog post describing it, but you can
start with the documentation in this file:
https://github.com/janestreet/core_kernel/blob/master/src/quickcheck_generator.mli
On Sun, Sep 13, 2015 at 11:52 AM, Simon Cruanes <simon.cruanes.2007@m4x.org>
wrote:
> There is also qtest (also called iTeML on github) which is a bit
> special: it's a testing framework providing unit testing through OUnit,
> and simple random testing; its specificy is that tests can be written in
> comments within the module to test, so that the code itself has no
> additional
> dependencies or code bloat due to tests. It is very easy to write new
> tests, since you don't have to add specific test modules.
> It is used, afaik, at least in Batteries and in containers.
>
> I am probably going to work on making qtest and qcheck a bit closer, if
> qtest's developper(s) agree.
>
> Cheers,
>
> Le Sun, 13 Sep 2015, Török Edwin a écrit :
> > On 09/13/2015 11:09 AM, Keiko Nakata wrote:
> > > Hi,
> > >
> > > I am looking for (reasonably matured and hopefully easy to install)
> QuickCheck-like property based testing software for OCaml code.
> > >
> > > Any information is appreciated!
> >
> > There is qcheck.0.4, quickcheck.1.0.2 and kaputt.1.2 on opam.
> > qcheck has documentation in the mli, integration with OUnit and quite
> easy to get started with.
> > Kaputt also has reducers (to produce smaller counterexamples), and
> SmallCheck-like enumeration tests.
> >
> > I haven't tried quickcheck, and haven't found an equivalent to
> SmartCheck's counterexample generalization [1]
> >
> > [1] https://www.cs.indiana.edu/~lepike/pubs/smartcheck.pdf
> >
> > Best regards,
> > --Edwin
> >
> > --
> > 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
>
>
> --
> Simon Cruanes
>
> http://weusepgp.info/
> key 49AA62B6, fingerprint 949F EB87 8F06 59C6 D7D3 7D8D 4AC0 1D08 49AA
> 62B6
>
[-- Attachment #2: Type: text/html, Size: 3355 bytes --]
next prev parent reply other threads:[~2015-09-15 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 8:09 Keiko Nakata
2015-09-13 8:42 ` Török Edwin
2015-09-13 15:52 ` Simon Cruanes
2015-09-15 13:09 ` Yaron Minsky [this message]
2015-09-15 14:06 ` Gabriel Scherer
2015-09-15 14:21 ` Carl Eastlund
2015-09-15 14:30 ` Simon Cruanes
2015-09-15 14:44 ` Carl Eastlund
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=CACLX4jR2W+Q2--O+YPBYM8k0tSBES9JxRDVfju9y1QR3D89OTg@mail.gmail.com \
--to=yminsky@janestreet.com \
--cc=caml-list@inria.fr \
--cc=ceastlund@janestreet.com \
--cc=edwin+ml-ocaml@etorok.net \
--cc=simon.cruanes.2007@m4x.org \
/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