From 6b1cbda1b9e0e8f29c0a6e4e44ce2d5a2aee974f Mon Sep 17 00:00:00 2001
From: Theophile Ranquet <ranquet@lrde.epita.fr>
Date: Mon, 22 Oct 2012 14:19:31 +0000
Subject: [PATCH] misc: document TESTSUITEFLAGS in README-hacking

* README-hacking: Document -j and -k flags.
---
 README-hacking | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/README-hacking b/README-hacking
index 988bd304..ff5b4345 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, 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]]). Categories include:
+  - 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
 
-- 
2.45.2