Re: [Caml-list] testing private functions with oUnit

[Francois Berenger <francois.berenger@inria.fr>]

On 09/29/2014 09:08 AM, Malcolm Matalka wrote:
> Out of curiosity: why?  Any private function should be exercised through
> an API function somehow.
>
> IME, testing private functions often makes refactoring more painful
> without a clear win in code being better tested.
>
> If your API is pure, btw, you should checkout QCheck for testing it
> instead of unit tests.

You can also use qtest (available in opam) and write your test code 
directly as comments in the .ml files, as is done in batteries:

https://github.com/ocaml-batteries-team/batteries-included/blob/master/src/batList.mlv

Look for (*$T in the code for example.

> My 2 cents,
> /M
>
> Eric Cooper <ecc@cmu.edu> writes:
>
>> I'd like to write unit tests for functions not exported in a .mli
>> file.  The only way I can see is to remove the .mli file while
>> building the test, so the whole .ml file is visible.  Is there a better
>> way, preferably integrated with ocamlmake + findlib?
>>
>> --
>> Eric Cooper             e c c @ c m u . e d u
>

-- 
Regards,
Francois.