Re: [Caml-list] Use of unit testing frameworks in OCaml

["Daniel Bünzli" <daniel.buenzli@erratique.ch>]

Le mercredi, 9 septembre 2015 à 23:29, John Christopher McAlpine a écrit :
> Here you go: https://github.com/michipili/broken

Looking at the examples it really seems to be.

Names are already hard to come by, why bother me with having to invent one for *each* assertion ? What you want is to subvert the backtrace mechanism so that failing tests just output a location your IDE can jump to and highlight.  

Also for tests that are more complex than simple assertions I'd like to have a print out of the function arguments that lead to the assertion failure. See for example [1] for a toy testing framework that does that and that I c&p around because I don't have the time to spend a month to give the problem a good solution. This simple thing is already, from a programmer perspective, much better than anything you mentioned — but it's missing the quickcheck and random value generation bits that any self-respecting solution should bring to the table.  

The problem (beyond Gabriel's more sensitive answer) with these all these testing framework is that they seem to be too busy to uncreatively copy the useless crap oo testing framework and terminology rather than provide actual useful tools for programmers.

Best,

Daniel

[1]
https://github.com/dbuenzli/astring/blob/master/test/testing.mli
https://github.com/dbuenzli/astring/blob/master/test/testing.ml