Safe Haskell | None |
---|---|
Language | Haskell2010 |
Unit testing support for tasty, inspired by the HUnit package
- testCase :: TestName -> Assertion -> TestTree
- testCaseInfo :: TestName -> IO String -> TestTree
- testCaseSteps :: TestName -> ((String -> IO ()) -> Assertion) -> TestTree
- type Assertion = IO ()
- assertFailure :: String -> Assertion
- assertBool :: String -> Bool -> Assertion
- assertString :: String -> Assertion
- assertEqual :: (Eq a, Show a) => String -> a -> a -> Assertion
- class Assertable t where
- type AssertionPredicate = IO Bool
- class AssertionPredicable t where
- assertionPredicate :: t -> AssertionPredicate
- (@?) :: AssertionPredicable t => t -> String -> Assertion
- (@=?) :: (Eq a, Show a) => a -> a -> Assertion
- (@?=) :: (Eq a, Show a) => a -> a -> Assertion
- data HUnitFailure = HUnitFailure String
Documentation
testCaseInfo :: TestName -> IO String -> TestTree Source
Like testCase
, except in case the test succeeds, the returned string
will be shown as the description. If the empty string is returned, it
will be ignored.
testCaseSteps :: TestName -> ((String -> IO ()) -> Assertion) -> TestTree Source
Create a multi-step unit test.
Example:
main = defaultMain $ testCaseSteps "Multi-step test" $ \step -> do step "Preparing..." -- do something step "Running part 1" -- do something step "Running part 2" -- do something assertFailure "BAM!" step "Running part 3" -- do something
The step
calls are mere annotations. They let you see which steps were
performed successfully, and which step failed.
You can think of step
as putStrLn
, except putStrLn
would mess up the output with the
console reporter and get lost with the others.
For the example above, the output will be
Multi-step test: FAIL Preparing... Running part 1 Running part 2 BAM! 1 out of 1 tests failed (0.00s)
Note that:
- Tasty still treats this as a single test, even though it consists of multiple steps.
- The execution stops after the first failure. When we are looking at a failed test, we know that all displayed steps but the last one were successful, and the last one failed. The steps after the failed one are not displayed, since they didn't run.
When an assertion is evaluated, it will output a message if and only if the assertion fails.
Test cases are composed of a sequence of one or more assertions.
Unconditionally signals that a failure has occured. All other assertions can be expressed with the form:
if conditionIsMet then IO () else assertFailure msg
Asserts that the specified condition holds.
Signals an assertion failure if a non-empty message (i.e., a message
other than ""
) is passed.
:: (Eq a, Show a) | |
=> String | The message prefix |
-> a | The expected value |
-> a | The actual value |
-> Assertion |
Asserts that the specified actual value is equal to the expected value. The output message will contain the prefix, the expected value, and the actual value.
If the prefix is the empty string (i.e., ""
), then the prefix is omitted
and only the expected and actual values are output.
class Assertable t where Source
Allows the extension of the assertion mechanism.
Since an Assertion
can be a sequence of Assertion
s and IO
actions,
there is a fair amount of flexibility of what can be achieved. As a rule,
the resulting Assertion
should be the body of a TestCase
or part of
a TestCase
; it should not be used to assert multiple, independent
conditions.
If more complex arrangements of assertions are needed, Test
s and
Testable
should be used.
Assertable Bool | |
Assertable String | |
Assertable () | |
Assertable t => Assertable (IO t) |
type AssertionPredicate = IO Bool Source
The result of an assertion that hasn't been evaluated yet.
Most test cases follow the following steps:
- Do some processing or an action.
- Assert certain conditions.
However, this flow is not always suitable. AssertionPredicate
allows for
additional steps to be inserted without the initial action to be affected
by side effects. Additionally, clean-up can be done before the test case
has a chance to end. A potential work flow is:
- Write data to a file.
- Read data from a file, evaluate conditions.
- Clean up the file.
- Assert that the side effects of the read operation meet certain conditions.
- Assert that the conditions evaluated in step 2 are met.
class AssertionPredicable t where Source
Used to signify that a data type can be converted to an assertion predicate.
:: AssertionPredicable t | |
=> t | A value of which the asserted condition is predicated |
-> String | A message that is displayed if the assertion fails |
-> Assertion |
Asserts that the condition obtained from the specified
AssertionPredicable
holds.
Asserts that the specified actual value is equal to the expected value (with the expected value on the left-hand side).
Asserts that the specified actual value is equal to the expected value (with the actual value on the left-hand side).
data HUnitFailure Source
Exception thrown by assertFailure
etc.