]> xenbits.xensource.com Git - libvirt.git/commitdiff
docs: hacking: demonstrate the powers of VIR_TEST_RANGE
authorJán Tomko <jtomko@redhat.com>
Fri, 18 Oct 2019 21:03:27 +0000 (23:03 +0200)
committerJán Tomko <jtomko@redhat.com>
Tue, 22 Oct 2019 20:09:13 +0000 (22:09 +0200)
Mention a more complex example.

Invoke the test without 'make' since the mentioned example
does not seem to be working anymore.

Signed-off-by: Ján Tomko <jtomko@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
docs/hacking.html.in

index cad0f1e8c1b61caa99cdb89b8a389c9e8991aa67..793a6b7e592ca9bbfad53468223bb5c4c5785460 100644 (file)
 
         <p>
           When debugging failures during development, it is possible
-          to focus in on just the failing subtests by using TESTS and
-          VIR_TEST_RANGE:
+          to focus in on just the failing subtests by using
+          VIR_TEST_RANGE. I.e. to run all tests from 3 to 20 with the
+          exception of tests 6 and 16, use:
         </p>
 
 <pre>
-  make check VIR_TEST_DEBUG=1 VIR_TEST_RANGE=3-5 TESTS=qemuxml2argvtest
+  VIR_TEST_DEBUG=1 VIR_TEST_RANGE=3-5,7-20,^16 ./run tests/qemuxml2argvtest
 </pre>
 
         <p>