aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown/IDE-integration.md
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2019-12-12 23:47:10 +0100
committerJussi Pakkanen <jpakkane@gmail.com>2019-12-13 00:47:10 +0200
commit3778a34979c1f705eda044960cc1f89233409f88 (patch)
tree9a52f95bb448ebcbe4249325c2c2d7b37e72bf2d /docs/markdown/IDE-integration.md
parent9371965132e8854db1b43b4bda61f0404b4b3609 (diff)
downloadmeson-3778a34979c1f705eda044960cc1f89233409f88.zip
meson-3778a34979c1f705eda044960cc1f89233409f88.tar.gz
meson-3778a34979c1f705eda044960cc1f89233409f88.tar.bz2
mintro: include test protocol in introspection data
Diffstat (limited to 'docs/markdown/IDE-integration.md')
-rw-r--r--docs/markdown/IDE-integration.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/markdown/IDE-integration.md b/docs/markdown/IDE-integration.md
index 1c66d53..77e00bd 100644
--- a/docs/markdown/IDE-integration.md
+++ b/docs/markdown/IDE-integration.md
@@ -235,7 +235,7 @@ When these tests fail, the user probably wants to run the failing test in a
debugger. To make this as integrated as possible, extract the tests from the
`intro-tests.json` and `intro-benchmarks.json` files. This provides you with
all the information needed to run the test: what command to execute, command
-line arguments and environment variable settings.
+line arguments, environment variable settings and how to process the output.
```json
{
@@ -244,6 +244,7 @@ line arguments and environment variable settings.
"timeout": "the test timeout",
"suite": ["list", "of", "test", "suites"],
"is_parallel": true / false,
+ "protocol": "exitcode" / "tap",
"cmd": ["command", "to", "run"],
"env": {
"VARIABLE1": "value 1",