[Haskell-cafe] Recipes for organizing HUnit tests

[Mushfeq Khan]

I'm new to Haskell and am trying to find a good way to organize my HUnit
tests. Having used some of the other XUnit frameworks, I tended towards
trying to organize them all in a parallel "test" folder structure, but this
seems to be a bad fit for Haskell, since the test modules cannot see the
source modules unless they are either in the same folder or a folder above
it. That's without modifying the module search path when I run the tests,
which I would like to avoid.

So I tried looking for examples of HUnit-tested source code out there and
found that the cryptographic library Crypto has some unit tests. However,
Crypto seems to place all its test code at the top of the folder hierarchy
for the reasons I mentioned above. This turns out to be fine for Crypto
since there are few tests. But I can foresee the tests for my project
multiplying to the point where it would become very unsightly to put them
all in the top-level folder.

My questions to you are: how do you organize your HUnit/QuickCheck tests? Is
there a convention? Is there some library out there that embodies this
convention?

Mushfeq.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.haskell.org/pipermail/haskell-cafe/attachments/20071028/fe8174b2/attachment.htm