summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'dev-haskell/tasty-expected-failure/metadata.xml')
-rw-r--r--dev-haskell/tasty-expected-failure/metadata.xml23
1 files changed, 5 insertions, 18 deletions
diff --git a/dev-haskell/tasty-expected-failure/metadata.xml b/dev-haskell/tasty-expected-failure/metadata.xml
index c1dbe8030a14..ba8a08351743 100644
--- a/dev-haskell/tasty-expected-failure/metadata.xml
+++ b/dev-haskell/tasty-expected-failure/metadata.xml
@@ -1,25 +1,12 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<!DOCTYPE pkgmetadata SYSTEM "https://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>
+ <upstream>
+ <remote-id type="hackage">tasty-expected-failure</remote-id>
+ <remote-id type="github">nomeata/tasty-expected-failure</remote-id>
+ </upstream>
</pkgmetadata>