<div dir="ltr"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div class="gmail_quote"><div class="Ih2E3d">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">How do folks like to package up QuickCheck tests for their libraries? In the main library? As a separate repo & package? Same repo & separate package? Keeping tests with the tested code allows testing of non-exported functionality, but can add quite a lot of clutter.<br>
</div></blockquote></div></div><div><br>I have QuickCheck properties plus HUnit tests, but I think the question is the same. For me, it's in the same repository and shipped with the package source. I think that if you ship source (even via Hackage), you should also ship tests. So, if somebody wants to modify the source, they can run the tests. And making it convenient to test is very important, so I have "cabal test" (or "runhaskell Setup.hs test" without cabal-install) configured to run the tests. I don't think tests should (in general) be part of the user-visible API, so I have them external to the module hierarchy.</div>
</div></div></div></div></blockquote></div><div> <br>How do you set up cabal to do these tests?<br></div></div></div></blockquote><div><br>I use the "runTests" hook in Distribution.Simple. The code below works on Windows and Mac, because that's what we use.<br>
<br>\begin{code}<br>module Main (main) where<br><br>import Distribution.Simple<br>import System.Cmd (system)<br>import System.FilePath ((</>))<br><br>main :: IO ()<br>main = defaultMainWithHooks hooks where<br> hooks = simpleUserHooks { runTests = runTests' }<br>
<br>runTests' _ _ _ _ = system cmd >> return ()<br> where testdir = "dist" </> "build" </> "test"<br> testcmd = "." </> "test"<br> cmd = "cd " ++ testdir ++ " && " ++ testcmd<br>
\end{code}<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div class="gmail_quote"><div>Do your libraries depend on HUnit?<br>
</div></div></div></blockquote><div><br>No, because I use an ultra-secret trick. ;) I have a Library in my .cabal file and an Executable for testing. Part of the test description follows.<br><br>\begin{cabal}<br>Executable test<br>
hs-source-dirs: src, tests, examples<br> main-is: Main.hs<br><br> -- Only enable the build-depends here if configured with "-ftest". This<br> -- keeps users from having to install QuickCheck 2 in order to use EMGM.<br>
if flag(test)<br> build-depends: QuickCheck >= 2.0, HUnit >= 1.2<br> else<br> buildable: False<br>\end{cabal}<br><br>With that last flag-based if/else, I hide the dependencies for normal building ('test' by default is False). If 'test' is False, then the executable also cannot be built.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div class="gmail_quote"><div>Where do you like to place your tests? In the functionality modules? A parallel structure? A single Test.hs file somewhere?<br>
</div><div class="Ih2E3d"><div></div></div></div></div></blockquote><div><br>In a separate "tests" directory at the same level as the "src" directory containing the module hierarchy. It has a number of files, mostly one per module tested.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div class="gmail_quote"><div class="Ih2E3d"><div><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
Testing non-exported functionality without exporting the test interface seems difficult in general. Is there a way to hide part of a module interface with Cabal? Then, you could have a 'test' function exported from each module for testing but hidden for release.<br>
</blockquote>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div>
</div><div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">My current leaning is to split a package "foo" into packages "foo" and "foo-test"<br>
</div></blockquote><div> </div></div></div></div><div>What benefit does this provide?</div></div></div></div></blockquote></div><div><br>It keeps the library and its dependencies small. Probably some of the alternatives do as well. For testing, I'm using <a href="http://haskell.org/haskellwiki/Checkers" target="_blank">checkers</a> in addition to QuickCheck, and I'd prefer not to make casual library users have to pull in those libraries as well.<br>
</div></div></div></blockquote><div><br>Ah, so you're handling the same problem we are in a different way. Nice!<br><br>Sean<br></div></div></div>