diff options
| author | V3n3RiX <venerix@redcorelinux.org> | 2020-08-25 10:45:55 +0100 |
|---|---|---|
| committer | V3n3RiX <venerix@redcorelinux.org> | 2020-08-25 10:45:55 +0100 |
| commit | 3cf7c3ef441822c889356fd1812ebf2944a59851 (patch) | |
| tree | c513fe68548b40365c1c2ebfe35c58ad431cdd77 /dev-haskell/tasty-expected-failure/metadata.xml | |
| parent | 05b8b0e0af1d72e51a3ee61522941bf7605cd01c (diff) | |
gentoo resync : 25.08.2020
Diffstat (limited to 'dev-haskell/tasty-expected-failure/metadata.xml')
| -rw-r--r-- | dev-haskell/tasty-expected-failure/metadata.xml | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/dev-haskell/tasty-expected-failure/metadata.xml b/dev-haskell/tasty-expected-failure/metadata.xml new file mode 100644 index 000000000000..38e4a3a924f5 --- /dev/null +++ b/dev-haskell/tasty-expected-failure/metadata.xml @@ -0,0 +1,25 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> +<pkgmetadata> + <maintainer type="project"> + <email>haskell@gentoo.org</email> + <name>Gentoo Haskell</name> + </maintainer> + <longdescription> + 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.warpTest', which is also provided. + </longdescription> +</pkgmetadata> |