summaryrefslogtreecommitdiff
path: root/dev-haskell/tasty-expected-failure
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2021-03-20 14:27:17 +0000
committerV3n3RiX <venerix@redcorelinux.org>2021-03-20 14:27:17 +0000
commit5bb9ff1ee56d2b5e75e01a7f066d8b0cec84ec02 (patch)
tree66e860a5099bcad013f1cf667255dc372a7c11b3 /dev-haskell/tasty-expected-failure
parent7218e1b46bceac05841e90472501742d905fb3fc (diff)
gentoo resync : 20.03.2021
Diffstat (limited to 'dev-haskell/tasty-expected-failure')
-rw-r--r--dev-haskell/tasty-expected-failure/Manifest2
-rw-r--r--dev-haskell/tasty-expected-failure/metadata.xml12
2 files changed, 7 insertions, 7 deletions
diff --git a/dev-haskell/tasty-expected-failure/Manifest b/dev-haskell/tasty-expected-failure/Manifest
index 534ca8c01a21..0155654766cc 100644
--- a/dev-haskell/tasty-expected-failure/Manifest
+++ b/dev-haskell/tasty-expected-failure/Manifest
@@ -1,3 +1,3 @@
DIST tasty-expected-failure-0.11.1.2.tar.gz 3781 BLAKE2B 04101b477457747abbf1a90fed80ab8692e3f771f27fae8310c0451839b38efadf1751ae302a1bac0f020e01533030563c45a2c0d75b03f9cda88ee23d1d8e12 SHA512 31f89d64a1f700a2563b291d287f559e023b0b1059cf5ad35eb9a8b2d4a7d90b2ffced828017b3e86d7ece0b125787f7512e9f4745c75d38bbc688e09031aae5
EBUILD tasty-expected-failure-0.11.1.2.ebuild 745 BLAKE2B b635671f6f37788177f8ea8315558102b0bc80b45107b7f7bfcca1ffaca423ba1b184eccb19abcc67c952c3a3fce3108a383a9f83e0521b0ebebb3a9050a21cb SHA512 6a0d37ea7eda7932fe7128a53d3f01fd229ac152d715891e2219b2363e89fd7b8cbf74241582a1c9f9ca841f0a682aa3662f7792776cb7aebb71432982066b27
-MISC metadata.xml 1198 BLAKE2B 916fc5054a8fba5dafbea48bb7074ab2bcbd986191298d2a985b9d89f4db424d38277f4229baec55c5b327fd8142aa2510e0d001f69818248480009e2e7a2285 SHA512 1c2e7390095a26f26d3fb57b7715fe34afb209b63761e3597e578d72169b8b6f802361adfa15652c054560c210707dee0d00c43326e82c73eec7ff4df70e72d1
+MISC metadata.xml 1148 BLAKE2B 29cc955f3d652472632fb2e17400a7fd51dc82ccd167c7194566fe444f7dc80d486ad457bf59ca0cb98650643990229712af498555c944c2d29856fff31b2326 SHA512 07c1482566c466ab9ddd401ab3e1d3bf407b14550eca0d55e3ed34733b127097dc36c2b1362c9aad2b70f433bfc2f95935932e64cbc5a7edc3520e7eff22ae13
diff --git a/dev-haskell/tasty-expected-failure/metadata.xml b/dev-haskell/tasty-expected-failure/metadata.xml
index 38e4a3a924f5..c1dbe8030a14 100644
--- a/dev-haskell/tasty-expected-failure/metadata.xml
+++ b/dev-haskell/tasty-expected-failure/metadata.xml
@@ -6,20 +6,20 @@
<name>Gentoo Haskell</name>
</maintainer>
<longdescription>
- With the function &#39;Test.Tasty.ExpectedFailure.expectFail&#39; in the provided module
- &quot;Test.Tasty.ExpectedFailure&quot;, you can mark that you expect test cases to fail,
+ 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 &#39;Test.Tasty.ExpectedFailure.expectFail&#39;, and you can still push
+ 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 &#39;Test.Tasty.ExpectedFailure.expectFail&#39; marker.
+ can remove the 'Test.Tasty.ExpectedFailure.expectFail' marker.
- The module also provides &#39;Test.Tasty.ExpectedFailure.ignoreTest&#39; to avoid
+ The module also provides 'Test.Tasty.ExpectedFailure.ignoreTest' to avoid
running a test. Both funtions are implemented via the more general
- &#39;Test.Tasty.ExpectedFailure.warpTest&#39;, which is also provided.
+ 'Test.Tasty.ExpectedFailure.warpTest', which is also provided.
</longdescription>
</pkgmetadata>