Skip to content

Better QuickCheck/HUnit integration

Daniel Burrows <dburrows@debian.org> in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355215 requests:

Quickcheck and HUnit are both great tools for testing software, but it seems to be rather difficult to make them work together. In particular, since the signature of all the quickCheck interface functions is some variant on

Testable a => a -> IO ()

the only way to find out whether a test succeeded or failed is to read the terminal output. It would be ideal if !QuickCheck could generate HUnit assertion failures when a test failed (maybe by expanding the Config structure with "failure hooks"), but even just changing its signature to either

Testable a => a -> IO Bool

returning True for success, or (slightly more ambitiously)

Testable a => a -> IO (Maybe String)

returning Nothing for success and an error message otherwise would be enough to get basic integration working.

Trac metadata
Trac field Value
Version 6.6.1
Type FeatureRequest
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component libraries (other)
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system Unknown
Architecture Unknown
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information