X-Git-Url: https://arthur.barton.de/gitweb/?a=blobdiff_plain;f=HACKING;h=d62cfc74a2c6ed76019a8bea4aecc83f8e7efc34;hb=338beb8d14749263bcefdde992d1ce6110b52bce;hp=6ecab7ea3bd29c72e909effcd78e7c246f73ac0f;hpb=82fe455b6c6f57db8f062bf27af4c7ddb2e83226;p=bup.git

diff --git a/HACKING b/HACKING
index 6ecab7e..d62cfc7 100644
--- 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,6 +57,24 @@ 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
 ==================
 
@@ -96,7 +112,7 @@ Of course, unless your machine is set up to handle outgoing mail
 locally, you may need to configure git to be able to send mail.  See
 git-send-email(1) for further details.
 
-Oh, and we do have a ./CODING-STYLE, hobgoblins and all, though don't
+Oh, and we do have a ./CODINGSTYLE, hobgoblins and all, though don't
 let that scare you off.  We're not all that fierce.