X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=regress%2FREADME;h=0f2037bb05bf060eeddb110a86d60499df793ae5;hb=ebd87d08c7bea6916cc6005c98de4cdcfc30824c;hp=09dbc73bbefce3931902acd06a135e5135eff348;hpb=52ffaeed2cf3b0fc601c11a565c983555334bbc9;p=bacula%2Fbacula

diff --git a/regress/README b/regress/README
index 09dbc73bbe..0f2037bb05 100644
--- a/regress/README
+++ b/regress/README
@@ -13,13 +13,12 @@ system uses MySQL, you can use SQLite here.
 
 
 To set it up, create your personal configuration file, by
-copying prototype.conf to xxx.conf or simply editing prototype.conf
-directly.
+copying prototype.conf to config or simply editing prototype.conf
+directly then copying it to the file config.
 
-Then edit your conf file and define appropriate values
-for the variables that are in that file.  If you want to see
-a real example, look at kern.conf, but please don't use my
-email address!
+You must end up with a file named config in the main regress 
+directory that has all the specifications that correspond to
+your system.
 
 If you are using SQLite, make sure that depkgs is pre-built if it
 isn't already: (cd your-depkgs; make sqlite).
@@ -38,7 +37,6 @@ SQLite as the database, while my production uses MySQL.
 
 Then do:
 
-   ./config xxx.conf
    make setup
 
 You run the above one time.  This will build a Makefile from
@@ -56,6 +54,8 @@ self-initalizing and should clean up after itself.
 All the tests expect you to execute them from the main regress 
 directory!               
 
+Running the disk based tests:
+
 You can run all the disk based tests by doing:
 
   ./do_file
@@ -64,6 +64,8 @@ The disk based tests are totally separate from any production
 system, provided you have configured the database appropriately     
 as noted above.
 
+Running all the "standard" tests:
+
 You can run all the disk and most of the tape tests by doing:
 
   ./do_all
@@ -101,6 +103,24 @@ to do:
 
 this cleans up any files that may be created with root permissions.
 
+Tape test naming convention:
+
+I've renamed the tape tests to include an indication of how
+many tapes and drives each test needs.  The indication consists
+of 4 or 5 characters just before the final -tape.  For example,
+there is a tape test named:
+
+  vol-duration-2t1da-tape
+
+this means that it uses 2 tape (2t) one drive (1d) and the
+autochanger (a).  Another test might be named
+
+  fixed-block-size-1t1d-tape
+
+which means it uses one tape on one drive and no autochanger.
+
+Adding tests:
+
 If you want to add more tests, do so by putting the shell script 
 in the tests subdirectory. Be careful when adding (or better not)
 new clients, pools, and such to the test-bacula-dir.conf.in file
@@ -115,6 +135,7 @@ conf files, and you do not need a new copy of the source, you can simply do:
    make sed
 
 Debugging failed tests:
+
 Prior versions required editing the tests/xxxx and changing a debug flag.
 However, that has been replaced by two environment variables: