Commit ab92ae333 added a cool feature, but didn't document it.
* docs/hacking.html.in: Document debugging a subset of tests.
* HACKING: Regenerate.
Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>
---
Pushing under the trivial rule, as I found myself wanting to
use this during development today.
HACKING | 5 +++++
docs/hacking.html.in | 11 +++++++++++
2 files changed, 16 insertions(+)
diff --git a/HACKING b/HACKING
index 256e8ae..f9f8381 100644
--- a/HACKING
+++ b/HACKING
@@ -123,6 +123,11 @@ VIR_TEST_DEBUG may provide larger amounts of information:
VIR_TEST_DEBUG=1 make check (or)
VIR_TEST_DEBUG=2 make check
+When debugging failures during development, it is possible to focus in on just
+the failing subtests by using TESTS and VIR_TEST_RANGE:
+
+ make check VIR_TEST_DEBUG=1 VIR_TEST_RANGE=3-5 TESTS=qemuxml2argvtest
+
Also, individual tests can be run from inside the "tests/" directory, like:
./qemuxml2xmltest
diff --git a/docs/hacking.html.in b/docs/hacking.html.in
index 0892b73..543c77e 100644
--- a/docs/hacking.html.in
+++ b/docs/hacking.html.in
@@ -141,6 +141,17 @@
VIR_TEST_DEBUG=1 make check (or)
VIR_TEST_DEBUG=2 make check
</pre>
+
+ <p>
+ When debugging failures during development, it is possible
+ to focus in on just the failing subtests by using TESTS and
+ VIR_TEST_RANGE:
+ </p>
+
+<pre>
+ make check VIR_TEST_DEBUG=1 VIR_TEST_RANGE=3-5 TESTS=qemuxml2argvtest
+</pre>
+
<p>
Also, individual tests can be run from inside the <code>tests/</code>
directory, like:
--
1.8.3.1
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list