Move ext/test.sh to ext/test-misc to match test-* pattern

[bup.git] / HACKING

diff --git a/HACKING b/HACKING
index b2622dbc5a250cbaf618a48f949a651d52c4a03c..c7845730798762e99d82e33ee91ad288e0b63bef 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -19,24 +19,24 @@ via email.
 Current Trajectory
 ==================
 
 Current Trajectory
 ==================
 

-Now that we've finished the 0.29.3 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 transferring saves between repositories and rewriting
-    branches.
-
-and these are also under consideration:
+Now that we've finished the 0.31 release, we're working on 0.32, and
+although we're not certain which new features will be included, we're
+considering:

 
   - Better VFS performance for large repositories (i.e. fuse, ls,
     web...).
 
 
   - Better VFS performance for large repositories (i.e. fuse, ls,
     web...).
 

+  - Better VFS caching.
+
+  - Index improvements.
+

   - Incremental indexing via inotify.
 
   - Smarter (and quieter) handling of cross-filesystem metadata.
 
   - Incremental indexing via inotify.
 
   - Smarter (and quieter) handling of cross-filesystem metadata.
 

-  - Support for more general purpose push/pull of branches, saves, and
-    tags between repositories.  (See the bup-get patch series.)
+  - Encryption.
+
+  - Support for alternate remote storage APIs.

 
 If you have the time and inclination, please help review patches
 posted to the list, or post your own.  (See "ways to help" below.)
 
 If you have the time and inclination, please help review patches
 posted to the list, or post your own.  (See "ways to help" below.)


@@ -66,14 +66,25 @@ output (interleaved parallel test output), and inaccurate intermediate
 success/failure counts, but the final counts displayed should be
 correct.
 
 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 non-Python tests can be run via
+
+    ./wvtest run test/ext/TEST
+
+and if you'd like to see all of the test output, you can omit the
+wvtest run wrapper: `test/ext/TEST`.  Individual Python tests can be
+run via
+
+    ./pytest test/int/test_something.py
+
+Internal tests that test bup's code directly are located in test/int,
+and external tests that test bup from the outside, typically by
+running the executable, are located in test/ext.

 
 

-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"

 
 

+Some aspects of the environment are automatically restored after each
+test via fixtures in conftest.py, including the state of the
+environment variables and the working directory; the latter is reset
+to the top of the source tree.

 
 Submitting patches
 ==================
 
 Submitting patches
 ==================