<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Henning:<div class=""><br class=""></div><div class="">I’m quite interested in this, especially as doctest on GHC 8.10 has issues: <a href="https://github.com/sol/doctest/issues/264" class="">https://github.com/sol/doctest/issues/264</a> Furthermore, compiling doctests would be a huge performance boost and can speed up CI times significantly.</div><div class=""><br class=""></div><div class="">I’m curious why your new package does not support IO-tests. Is that a “current” limitation, or is there a fundamental reason why IO-tests ca not be supported using your approach.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">-Levent.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 1, 2020, at 3:15 AM, Henning Thielemann <<a href="mailto:lemming@henning-thielemann.de" class="">lemming@henning-thielemann.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">I have started an alternative implementation of 'doctest'. In contrast to the original one, doctest-extract extracts Haskell test-modules from doctest comments. This integrates better with Cabal and its package version resolution and the tests are compiled, not interpreted in GHCi. Disadvantage is that doctest-extract does not support all features of 'doctest', e.g. IO-tests.<br class=""><br class="">I uploaded a preview as package candidates to Hackage:<br class=""><br class="">$ cabal install $(for pkg in doctest-extract-0.0 doctest-lib-0.0 utility-ht-0.0.16 non-empty-0.3.3; do echo <a href="https://hackage.haskell.org/package/$pkg/candidate/$pkg.tar.gz" class="">https://hackage.haskell.org/package/$pkg/candidate/$pkg.tar.gz</a>; done)<br class=""><br class=""><br class="">Extract test modules like so:<br class=""><br class="">$ doctest-extract -i src/ -o test/ --executable-main=Test/Main.hs --import-tested $$(cat test-module.list)<br class=""><br class=""><br class="">There is still a problem: A failing QuickCheck test does not abort the whole test-suite. 'cabal test' will report success even if one QuickCheck property test fails. I wonder what is the proposed way to make a failing property fail the test-suite? I could use (QC.whenFail exitFailure). Is this the intended way?<br class="">_______________________________________________<br class="">Haskell-Cafe mailing list<br class="">To (un)subscribe, modify options or view archives go to:<br class=""><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe" class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe</a><br class="">Only members subscribed via the mailman list are allowed to post.</div></div></blockquote></div><br class=""></div></body></html>