Prefix your test case names and tasty-discover will discover, collect and run
them. All popular Haskell test libraries are covered. Configure once then just
write your tests. Avoid forgetting to add test modules to your Cabal/Hpack
files. Tasty ingredients are included along with various configuration options
for different use cases.

Create Test Driver File

You can name this file anything you want but it must contain the correct
preprocessor definition for tasty-discover to run and to detect the
configuration. It should be at the top level of the test directory.

For example (in test/Driver.hs):

{-# OPTIONS_GHC -F -pgmF tasty-discover #-}

Configure Cabal or Hpack Test Suite

In order for Cabal/Stack to know where the tests are, you’ll need to configure
the main-is option of your test-suite to point to the driver file. In the
following example, the test driver file is called Driver.hs:

Example Project

Change Log

We try to keep tagged releases in our release process, if you care about that.

Deprecation Policy

If a breaking change is implemented, you’ll see a major version increase, an
entry in the change log and a compile-time error with a deprecation warning
and clear instructions on how to upgrade. Please do complain if we’re doing
this too much.

Contributing

All contributions welcome! The continuous integration suite is pretty
comprehensive, so just get hacking and add a test case - there are plenty of
examples, so this should be simple - and I’ll get to review your change ASAP.