wvtest: set a very large timeout to disable test time colors

[bup.git] / HACKING

diff --git a/HACKING b/HACKING
index d5ac2f74c1850b2297424e43bf93169f0cdf54c8..2cc93a4f02c1fc1ff95c3b0d7a5a2e3dd5b655ed 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -19,12 +19,10 @@ via email.
 Current Trajectory
 ==================
 
-Now that we've finished the 0.27 release, we're working on 0.28, and
+Now that we've finished the 0.29.1 release, we're working on 0.30, and
 although we're not certain which new features will be included, here
 are likely candidates:
 
-  - Support for rm/gc.
-
   - Support for transferring saves between repositories and rewriting
     branches.
 
@@ -59,13 +57,31 @@ incorporating it into master, so reviews are an important way to help.
 We also love a good "Tested-by:" -- the more the merrier.
 
 
+Testing
+=======
+
+You can run the test suite much more quickly via "make -j test" (as
+compared to "make test"), at the expense of slightly more confusing
+output (interleaved parallel test output), and inaccurate intermediate
+success/failure counts, but the final counts displayed should be
+correct.
+
+Individual non-Python tests can be run via "./wvtest run t/TEST" and
+if you'd like to see all of the test output, you can omit the wvtest
+run wrapper: "t/TEST"
+
+Individual Python tests can be run via "./wvtest run ./wvtest.py
+lib/bup/t/TEST", and as above, you can see all the output by omitting
+the wvtest run wrapper like this: "./wvtest.py lib/bup/t/TEST"
+
+
 Submitting patches
 ==================
 
 As mentioned, all patches should be posted to the mailing list for
 review, and must be "signed off" by the author before official
 inclusion (see ./SIGNED-OFF-BY).  You can create a "signed off" set of
-patches in ./pending, ready for submission to the list, like this:
+patches in ./patches, ready for submission to the list, like this:
 
     git format-patch -s -o patches origin/master