From d5717bef93bef278a5b27276b1fc59f12ddc2b12 Mon Sep 17 00:00:00 2001 From: Martin Quinson Date: Sun, 1 Sep 2019 02:54:50 +0200 Subject: [PATCH] doc: specify that you need to build the tests before ctest --- docs/source/Installing_SimGrid.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/source/Installing_SimGrid.rst b/docs/source/Installing_SimGrid.rst index 8d2feb9ded..0c09c08ff9 100644 --- a/docs/source/Installing_SimGrid.rst +++ b/docs/source/Installing_SimGrid.rst @@ -335,12 +335,14 @@ Testing your build Once everything is built, you may want to test the result. SimGrid comes with an extensive set of regression tests (as described in the -@ref inside_tests "insider manual"). The tests are run with ``ctest``, -that comes with CMake. We run them every commit and the results are -on `our Jenkins `_. +@ref inside_tests "insider manual"). The tests are not built by +default, so you first have to build them with ``make tests``. You can +then run them with ``ctest``, that comes with CMake. We run them +every commit and the results are on `our Jenkins `_. .. code-block:: shell + make tests # Build the tests ctest # Launch all tests ctest -R s4u # Launch only the tests whose names match the string "s4u" ctest -j4 # Launch all tests in parallel, at most 4 concurrent jobs -- 2.20.1