Comments on: Waddaya know, testing WORKS!

By: Ivan Miljenovic

Ivan Miljenovic — Mon, 07 Dec 2009 14:10:54 +0000

In the end, I did something similar for graphviz (Spencer Janssen amongst others convinced me that hit should be part of the tarball). However, I also included a testing component into the overall library section, which is where the QC dependency gets added.

(Also, did WordPress screw up your dependency range for QuickCheck?)

By: John Lato

John Lato — Mon, 07 Dec 2009 12:57:11 +0000

The method provided by Andy Gill works, but the “build-depends:” field containing QuickCheck should only be visible when the correct flag is set. In “iteratee”, I use this:

if flag(buildTests)
build-depends:
QuickCheck >= 2 && = 0.2 && = 0.2 && < 0.3
else
executable: False
buildable: False

which works properly.

By: If wishes were tests, code would be perfect « <<Insert Name Here>>

Thu, 26 Nov 2009 04:19:45 +0000

[...] I’ve mentioned previously, I’m currently writing a QuickCheck-based test suite for graphviz. Overall, I’m quite [...]

By: Ivan Miljenovic

Ivan Miljenovic — Tue, 17 Nov 2009 04:47:07 +0000

Hmmm…. I’m sure there was a problem with a package which had something similar to yours (but only one flag) that kept pulling in quickcheck, so at the urging of users the developer removed the testing executable…

And I must say, that ChalkBoard looks rather cool, though your website lies in terms of what the latest version is…

By: andygillku

andygillku — Tue, 17 Nov 2009 04:18:35 +0000

I second the unnecessary compulsory dependency problem!

In ChalkBoard, we use code like this

flag chalkmark { Default: False }
Executable chalkboard-tests-chalkmark
if flag(all) || flag(chalkmark)
buildable: True
else
Buildable: False
Hs-Source-Dirs: .,tests/chalkmark
Ghc-Options: -O2 -auto
Main-Is: Main.hs

That is, the chalkmark test (and any dependencies) are turned *off* by default, but we can turn them on during development (using the -fall or -fchalkboard flag).