I made a library for using QuickCheck in Cabal’s detailed testing interface

There’s already a library cabal-test-quickcheck for this, but it’s not available for newer GHC versions. I made my own that offers a bit more functionality, but might be a bit more finicky to use. It’s cabal-detailed-quickcheck on Hackage.



What are the advantages of the detailed testing interface as opposed to using the usual exitcode-stdio-1.0 with, say, tasty?

It’s supposed to allow external tools to more easily interface with the system. It allows consumers of the test suite to change settings of a test using setOption, sort tests using tags, and know which groups of tests are safe to run in parallel. You can also have a test run partially and return a status report along with a new IO value that can be run to continue the process.

As far as I know, there’s no tools that currently take advantage of this, and the <1.0 version number suggests it’s not done with development, but it seems a reasonable system to me.

1 Like