tasty-expected-failure: Mark tasty tests as failure expected
With the function
Test.Tasty.ExpectedFailure.expectFail in the provided module
Test.Tasty.ExpectedFailure, you can mark that you expect test cases to fail,
and not to pass.
This can for example be used for test-driven development: Create the tests,
mark them with
Test.Tasty.ExpectedFailure.expectFail, and you can still push
to the main branch, without your continuous integration branch failing.
Once someone implements the feature or fixes the bug (maybe unknowingly), the
test suite will tell him so, due to the now unexpectedly passing test, and he
can remove the
The module also provides
Test.Tasty.ExpectedFailure.ignoreTest to avoid
running a test. Both funtions are implemented via the more general
Test.Tasty.ExpectedFailure.wrapTest, which is also provided.
[Skip to Readme]
|Versions [RSS] [faq]||0.11, 0.11.0.1, 0.11.0.2, 0.11.0.3, 0.11.0.4, 0.11.1, 0.11.1.1, 0.11.1.2, 0.12, 0.12.1, 0.12.2, 0.12.3|
|Dependencies||base (>=4.5 && <4.11), tagged (>=0.7 && <0.9), tasty (>=0.11) [details]|
|Copyright||2015 Joachim Breitner|
|Revised||Revision 1 made by JoachimBreitner at 2017-05-16T22:14:07Z|
|Source repo||head: git clone git://github.com/nomeata/tasty-expected-failure|
|Uploaded||by JoachimBreitner at 2016-06-08T09:37:58Z|
|Distributions||Arch:0.12.3, Debian:0.11.1.1, LTSHaskell:0.12.3, NixOS:0.12.3, Stackage:0.12.3|
|Downloads||11250 total (254 in the last 30 days)|
|Rating||2.0 (votes: 1) [estimated by Bayesian average]|
Docs available [build log]
Last success reported on 2016-06-08 [all 1 reports]
- tasty-expected-failure-0.11.0.4.tar.gz [browse] (Cabal source package)
- Package description (revised from the package)
Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.
For package maintainers and hackage trustees