diff options
| author |  Jeremie Guichard <djebrest@gmail.com> | 2018-04-09 07:59:33 +0200 |
|---|---|---|
| committer |  Dirk Hohndel <dirk@hohndel.org> | 2018-04-09 07:48:01 -0700 |
| commit | f633cb81ae095ea128a406e69b5eecab23be92a9 (patch) | |
| tree | 2a0737a74ff7007b51570488413ce9435f98976f /Readme.testing | |
| parent | d64c48855df647cc4d80fba6874ae6f89511f7d3 (diff) | |
| download | subsurface-f633cb81ae095ea128a406e69b5eecab23be92a9.tar.gz | |
Fix minor typos and spelling mistakes in README.md and related
Signed-off-by: Jeremie Guichard <djebrest@gmail.com>
Diffstat (limited to 'Readme.testing')
| -rw-r--r-- | Readme.testing | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Readme.testing b/Readme.testing index a229e3a16..bab813110 100644 --- a/Readme.testing +++ b/Readme.testing @@ -5,11 +5,11 @@ to compile the source code of the tests and run them. 1 - create a folder 'build-tests' on the project root directory 2 - run cmake ( cmake .. ) -3 - compile the software by invocking make -4 - run the tests by invocking make test +3 - compile the software by invoking make +4 - run the tests by invoking make test (optional 5) if the tests are failing, a better way to see what's happening is to run ctest -V , this way the tests will still fail, -but more verbosically - easyer to track them down. +but more verbosely - easier to track them down. to create a new test, just implement copy the one provided by example in the tests folder and add the last three lines of the CMakeLists.txt file |