aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authortextshell <textshell@users.noreply.github.com>2018-12-30 22:35:42 +0100
committerDaniel Mensinger <daniel@mensinger-ka.de>2019-01-06 12:19:32 +0100
commitfb4bdd3330b5857cc0187dec1c75f307fe8889f8 (patch)
tree247f44156afb25fd01462f44134182983d84e5ee /docs
parent1e374feb1ce09e866f9625a3ea378b58fddaf768 (diff)
downloadmeson-fb4bdd3330b5857cc0187dec1c75f307fe8889f8.zip
meson-fb4bdd3330b5857cc0187dec1c75f307fe8889f8.tar.gz
meson-fb4bdd3330b5857cc0187dec1c75f307fe8889f8.tar.bz2
Update docs/markdown/IDE-integration.md
Co-Authored-By: mensinda <daniel@mensinger-ka.de>
Diffstat (limited to 'docs')
-rw-r--r--docs/markdown/IDE-integration.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/markdown/IDE-integration.md b/docs/markdown/IDE-integration.md
index 1b79c74..81fd43f 100644
--- a/docs/markdown/IDE-integration.md
+++ b/docs/markdown/IDE-integration.md
@@ -128,7 +128,7 @@ Because of this options for the subprojects can differ.
Compilation and unit tests are done as usual by running the `ninja` and `ninja test` commands. A JSON formatted result log can be found in `workspace/project/builddir/meson-logs/testlog.json`.
-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 `tests` and `benchmarks` entries.
+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.
```json