I’ve some doctests for elm functions which I’m exposing in the module statement. How are you doing this and making it clear the functions are only being exposed for elm-test (and elm-verify-examples)? Or do you not test such internal functions and only test the public API so that refactors are unh…

instead of exposing the function, I put it into a test record and expose that instead module Example exposing ( func - , helper + , test ) +test = + { helper = helper + } + + then I add test. prefix in my tests {-| - helper "k" + test.helper "k" --> False …

An elegant way to expose doctests to elm-test?

Learn

marciofrayze August 16, 2022, 12:20pm 2

No matter what language I’m using, I test only public APIs.

Topic		Replies	Views
Not exposing internals hurts testability Learn	29	3270	July 31, 2020
Tests and elm-format overwriting the exposing list Learn	4	823	November 9, 2018
[RFC] elm inline tests Request Feedback	7	834	June 16, 2019
Test-only values Show and Tell	7	1159	January 7, 2021
Advice on growing and maintaining a unit test suite for a SPA? Learn	5	1189	April 6, 2019

An elegant way to expose doctests to elm-test?

Related topics