aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2019-02-21 11:15:02 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2019-03-02 09:07:54 +0100
commit4b5cf3f7c549412e60baa925a42c80dbf17ffdd7 (patch)
tree9eff04bc89d5f45aebb902289b5dd5bce170a618 /docs/markdown
parentf0b0bcf86d195cc65918eea0de2c92083ac39f3f (diff)
downloadmeson-4b5cf3f7c549412e60baa925a42c80dbf17ffdd7.zip
meson-4b5cf3f7c549412e60baa925a42c80dbf17ffdd7.tar.gz
meson-4b5cf3f7c549412e60baa925a42c80dbf17ffdd7.tar.bz2
interpreter: add "protocol" kwarg to test
This is the first step towards adding support for TAP.
Diffstat (limited to 'docs/markdown')
-rw-r--r--docs/markdown/Reference-manual.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/docs/markdown/Reference-manual.md b/docs/markdown/Reference-manual.md
index 6c3b3ad..412135f 100644
--- a/docs/markdown/Reference-manual.md
+++ b/docs/markdown/Reference-manual.md
@@ -1406,10 +1406,7 @@ executable to run. The executable can be an [executable build target
object](#build-target-object) returned by
[`executable()`](#executable) or an [external program
object](#external-program-object) returned by
-[`find_program()`](#find_program). The executable's exit code is used
-by the test harness to record the outcome of the test, for example
-exit code zero indicates success. For more on the Meson test harness
-protocol read [Unit Tests](Unit-tests.md).
+[`find_program()`](#find_program).
Keyword arguments are the following:
@@ -1446,6 +1443,12 @@ Keyword arguments are the following:
before test is executed even if they have `build_by_default : false`.
Since 0.46.0
+- `protocol` specifies how the test results are parsed. For now
+ it must be `exitcode`, that is the executable's exit code is used
+ by the test harness to record the outcome of the test. For example
+ an exit code of zero indicates success. For more on the Meson test harness
+ protocol read [Unit Tests](Unit-tests.md). Since 0.50.0
+
Defined tests can be run in a backend-agnostic way by calling
`meson test` inside the build dir, or by using backend-specific
commands, such as `ninja test` or `msbuild RUN_TESTS.vcxproj`.