[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
README-hacking: details about make check-local
From: |
Akim Demaille |
Subject: |
README-hacking: details about make check-local |
Date: |
Fri, 5 Oct 2018 07:02:20 +0200 |
commit cf4600ca455a7d7c3d9c49c4ae26d2d7b118063d
Author: Akim Demaille <address@hidden>
Date: Sun Sep 30 16:32:22 2018 +0200
README-hacking: details about make check-local
diff --git a/README-hacking b/README-hacking
index 01d44429..4b92fcdd 100644
--- a/README-hacking
+++ b/README-hacking
@@ -190,12 +190,15 @@ Use liberally.
** TESTSUITEFLAGS
-The default is for make check to run all tests sequentially. This can be
-very time consumming when checking repeatedly or on slower setups. This can
-be sped up in two ways:
+To run just the testsuite (not the tests related to the examples), run `make
+check-local`.
+
+The default is for make check-local to run all tests sequentially. This can
+be very time consumming when checking repeatedly or on slower setups. This
+can be sped up in two ways:
Using -j, in a make-like fashion, for example:
- $ make check TESTSUITEFLAGS='-j8'
+ $ make check-local TESTSUITEFLAGS='-j8'
Running only the tests of a certain category, as specified in the AT files
with AT_KEYWORDS([[category]]). Categories include:
@@ -206,7 +209,7 @@ with AT_KEYWORDS([[category]]). Categories include:
- report, for automaton dumps
To run a specific set of tests, use -k (for "keyword"). For example:
- $ make check TESTSUITEFLAGS='-k c++'
+ $ make check-local TESTSUITEFLAGS='-k c++'
Both can be combined.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- README-hacking: details about make check-local,
Akim Demaille <=