summaryrefslogtreecommitdiff
blob: 38e4a3a924f5c35166e8d39728ee99913074e303 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
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 &#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,
		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
		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.
		
		The module also provides &#39;Test.Tasty.ExpectedFailure.ignoreTest&#39; to avoid
		running a test. Both funtions are implemented via the more general
		&#39;Test.Tasty.ExpectedFailure.warpTest&#39;, which is also provided.
	</longdescription>
</pkgmetadata>