Misc

[bacula/bacula] / regress / README

diff --git a/regress/README b/regress/README
index a087726a51bbf863e457a5cd509932aefd1599d5..ad5056c4e2cb21ff09e59a0f941ba49bf9663ce1 100644 (file)
--- a/regress/README
+++ b/regress/README
@@ -2,19 +2,32 @@
      Kern Sibbald
      April 2003
 
-This is Bacula's regression script directory.
+This is Bacula's regression script directory.  At this time
+(May 2003), it is still in development, so all the tests are
+not complete.
 
 To set it up, first edit Makefile and set BACULA-SOURCE to point
 to your source.
 
-Second, make sure that depkgs is in the parent directory of this
-directory (i.e. at the same level) and that it is pre-built.
+!!!!!!!!!! IMPORTANT !!!!!!!!
+Second, edit the EMAIL address in the Makefile to be your
+email address and not mine or I will get LOTS of unwanted
+email!
+
+Third, edit the DEPKGS path in the Makefile to point to the
+depkgs directory.
+
+Fourth, make sure that depkgs is pre-built if it isn't 
+already: (cd your-depkgs; make sqlite).
 
 Then do:
 
    make setup
 
-You run the above one time.
+You run the above one time.  This will copy the Bacula
+source, configure, build it, and configure all the scripts
+and conf files.  If you change your source, you will need
+to redo this command. 
 
 Then you can run any of the tests in the tests subdirectory.
 Each test whose name ends in -root requires you to be root for
@@ -24,7 +37,15 @@ self-initalizing and should clean up after itself.
 
 Not all the tests yet report OK.  This is simply because there are
 some spurious differences that I haven't yet taken the time to
-eliminate.
+eliminate.  The working scrips as of 24 Apr 03 are:
+
+backup-bacula-test
+sparse-test
+compressed-test
+sparse-compressed-test
+two-jobs-test
+wierd-files-test
+verify-vol-test
 
 The tests expect you to execute them from the main regress 
 directory!               
@@ -33,14 +54,15 @@ You can run them individually as:
 
    tests/two-jobs-test
 
-or all tests:
+or all non-root tests (my normal testing under my account)
+
+  ./all-non-root-tests
+
+or all tests (I only run these before a production release):
 
    su
    ./all-tests
 
-or all non-root tests
-
-  ./all-non-root-tests
 
 after running the root tests, while still root, it is a good idea
 to do:
@@ -49,3 +71,15 @@ to do:
 
 this cleans up any files that may be created with root permissions.
 
+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
+as it may invalidate a good number of tests, which respond to
+questions by answering with a number (i.e. the order of the selection
+list is known). It might be better to add your own testb-bacula...
+configuration file.  
+
+To avoid re-doing a make setup if you have made a change to the
+conf files, and you do not need a new copy of the source, you can simply do:
+
+   scripts/do-sed <your-email-address>