Re: [MirageOS-devel] OUnit Patch

[Mindy <mindy@xxxxxxxxxxxxxxxxxxx>]

On 10/29/2015 05:00 PM, Thomas Leonard wrote:
> On 29 October 2015 at 16:45, Rupert Horlick <rh572@xxxxxxxxx> wrote:
> > Hi Thomas,
> >
> > Iâve just been adding unit tests to my Mirage application using OUnit, but they 
> > started throwing up errors.
> >
> > I found your patch for the problem here 
> > (http://forge.ocamlcore.org/tracker/index.php?func=detail&aid=1363&group_id=162&atid=730),
> >  but I just wanted to ask what you think the best way to deal with this is?
> I guess oUnit is dead (that patch was first submitted in 2013). Maybe
> one of the other frameworks would be better, although the work-around
> is OK if you don't need to run tests in parallel. Mirage has alcotest,
> although I haven't used it in my own code:
>
> https://github.com/mirage/alcotest
>
> Perhaps someone on mirage-devel (CC'd) could give a quick overview of
> its benefits (apart from defaulting to not crashing, obviously)...
I've used Alcotest for several of my Mirage-related libraries. Alcotest 
has some nice features for running only subsets of tests across a couple 
of different dimensions (e.g. only tests in one list; only tests that 
have been tagged with "quick"), which is a handy thing to be able to 
do.  It's got nice features for dumping (or not dumping) error and 
non-error output, and reasonable default behavior around these things.
-Mindy

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel