From 505084f20b3908a1e14a443e578c585903594928 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Villemot?= <sebastien@dynare.org>
Date: Mon, 29 Jan 2024 13:56:59 +0100
Subject: [PATCH] README.md: fix testsuite documentation for running a whole
 directory of tests

[skip ci]
---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index fb14a555d7..7b188a42ad 100644
--- a/README.md
+++ b/README.md
@@ -149,9 +149,10 @@ Note that running the testsuite with Octave requires the additional packages `ps
 
 Often, it does not make sense to run the complete testsuite. For instance, if you modify codes only related to the perfect foresight model solver, you can decide to run only a subset of the integration tests, with:
 ```sh
-meson test -C <builddir> deterministic_simulations
+meson test -C <builddir> --suite deterministic_simulations
 ```
 This will run all the integration tests in `tests/deterministic_simulations`.
+This syntax also works with a nested directory (e.g. `--suite deterministic_simulations/purely_forward`).
 
 Finally if you want to run a single integration test, e.g. `deterministic_simulations/lbj/rbc.mod`:
 ```sh
-- 
GitLab