Run the test stack as a TestT with a log level of Crit.

Run the test stack as a TestT with a log level of Debug.

Run the test stack as a TestT with a log level of Trace.

Run the test stack as a TestT with the specified log level.

Run the test stack as a TestT with a log level of Crit and ChronosTime frozen at testTime.

Run the test stack as a TestT with a log level of Debug and ChronosTime frozen at testTime.

Run the test stack as a TestT with a log level of Trace and ChronosTime frozen at testTime.

Run the test stack as a TestT with the specified log level, with ChronosTime frozen at testTime.

The time at which the combinators ending in Frozen run the ChronosTime effect.

Interpret Stop by throwing a TestError, with the call site's stack.

Interpret an effect into Resumable by throwing a TestError for Stops, with the call site's stack.

Convert a TestT IO () to a TestTree ready for use with Tasty's machinery. This is for non-property tests that are supposed to be executed once.

Convert a TestT IO () to a TestTree ready for use with Tasty's machinery. This is for non-property tests that are supposed to be executed n times.

Parse the command line arguments and run the tests.

When the tests finish, this function calls exitWith with the exit code that indicates whether any tests have failed. Most external systems (stack, cabal, travis-ci, jenkins etc.) rely on the exit code to detect whether the tests pass. If you want to do something else after defaultMain returns, you need to catch the exception and then re-throw it. Example:

import Test.Tasty
import Test.Tasty.HUnit
import System.Exit
import Control.Exception

test = testCase "Test 1" (2 @?= 3)

main = defaultMain test
  `catch` (\e -> do
    if e == ExitSuccess
      then putStrLn "Yea"
      else putStrLn "Nay"
    throwIO e)

Create a named group of test cases or other groups

The main data structure defining a test suite.

It consists of individual test cases and properties, organized in named groups which form a tree-like hierarchy.

There is no generic way to create a test case. Instead, every test provider (tasty-hunit, tasty-smallcheck etc.) provides a function to turn a test case into a TestTree.

Groups can be created using testGroup.

Details on where and why a test failed.

The entirety of the effects handled by this module's interpreters.

An error that occured in the test machinery.