[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 4/4] misc: document TESTSUITEFLAGS in README-hacking
From: |
Theophile Ranquet |
Subject: |
[PATCH 4/4] misc: document TESTSUITEFLAGS in README-hacking |
Date: |
Wed, 24 Oct 2012 12:12:16 +0000 |
* README-hacking: Document -j and -k flags.
---
README-hacking | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/README-hacking b/README-hacking
index 988bd30..55b4e73 100644
--- a/README-hacking
+++ b/README-hacking
@@ -175,6 +175,28 @@ decide whether to update.
** make check
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:
+
+Using -j[integer], in a make-like fashion, for example:
+ $ make check TESTSUITEFLAGS='-j8'
+
+Running only the tests of a certain category, as specified in the AT files
+with AT_KEYWORDS([[category]]). Currently supported categories are:
+ - c++, for c++ parsers
+ - deprec, for tests concerning deprecated constructs.
+ - glr, for glr parsers
+ - java, for java parsers
+ - report, for automaton dumps
+
+To run a specific set of tests, use -k (for "keyword"). For example:
+ $ make check TESTSUITEFLAGS='-k c++'
+
+Both can be combined.
+
** Typical errors
If the test suite shows failures such as the following one
--
1.7.11.4