./devel/hs-tasty-expected-failure, Mark tasty tests as failure expected

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 0.12.3nb2, Package name: hs-tasty-expected-failure-0.12.3nb2, Maintainer: pkgsrc-users

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 Test.Tasty.ExpectedFailure.expectFail marker.

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.

Master sites:

Filesize: 5.875 KB

Version history: (Expand)

CVS history: (Expand)


   2025-03-05 04:40:14 by Masatake Daimon | Files touched by this commit (1173) 
Log message:
recursive revbump after patching lang/ghc910
   2025-02-02 14:06:08 by Masatake Daimon | Files touched by this commit (1173) 
Log message:
Bump all Haskell packages after switching the default compiler.
   2025-01-31 15:35:08 by Masatake Daimon | Files touched by this commit (5) 
Log message:
devel/hs-tasty-expected-failure: import hs-tasty-expected-failure-0.12.3

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 Test.Tasty.ExpectedFailure.expectFail marker.

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.