aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown
diff options
context:
space:
mode:
authorJussi Pakkanen <jpakkane@gmail.com>2019-04-21 15:15:19 +0300
committerGitHub <noreply@github.com>2019-04-21 15:15:19 +0300
commit91654674f0f060cdb4ad7356e453b6077c1b2565 (patch)
treed618819539827e631bb682f779bbd01844dbbd86 /docs/markdown
parent4e4f97edb3d475273108b203bc02b04bd6840b06 (diff)
parente43c9d96d1f90792a65457f94f8dbf58c2e475b3 (diff)
downloadmeson-91654674f0f060cdb4ad7356e453b6077c1b2565.zip
meson-91654674f0f060cdb4ad7356e453b6077c1b2565.tar.gz
meson-91654674f0f060cdb4ad7356e453b6077c1b2565.tar.bz2
Merge pull request #5289 from mesonbuild/fixxpass
Report xpass results as failures.
Diffstat (limited to 'docs/markdown')
-rw-r--r--docs/markdown/snippets/xfail.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/docs/markdown/snippets/xfail.md b/docs/markdown/snippets/xfail.md
new file mode 100644
index 0000000..5392fa9
--- /dev/null
+++ b/docs/markdown/snippets/xfail.md
@@ -0,0 +1,15 @@
+## Tests that should fail but did not are now errors
+
+You can tag a test as needing to fail like this:
+
+```meson
+test('shoulfail', exe, should_fail: true)
+```
+
+If the test passes the problem is reported in the error logs but due
+to a bug it was not reported in the test runner's exit code. Starting
+from this release the unexpected passes are properly reported in the
+test runner's exit code. This means that test runs that were passing
+in earlier versions of Meson will report failures with the current
+version. This is a good thing, though, since it reveals an error in
+your test suite that has, until now, gone unnoticed.