[Bacula-commits] SF.net SVN: bacula:[9103] trunk/regress/README

[<ke...@us...>]

Revision: 9103
          http://bacula.svn.sourceforge.net/bacula/?rev=9103&view=rev
Author:   kerns
Date:     2009-07-27 06:34:42 +0000 (Mon, 27 Jul 2009)

Log Message:
-----------
Update README for binary install tests

Modified Paths:
--------------
    trunk/regress/README

Modified: trunk/regress/README
===================================================================
--- trunk/regress/README	2009-07-26 17:05:18 UTC (rev 9102)
+++ trunk/regress/README	2009-07-27 06:34:42 UTC (rev 9103)
@@ -221,3 +221,35 @@
 info symbol 0x8082d58
 add_address(dlist**, IPADDR::i_type, unsigned short, int, char const*, char 
 const*, char**) + 568 in section .text
+
+Testing a Binary Installation:
+
+If you have installed your Bacula from a binary release such as (rpms or
+debs), you can still run regression tests on it.  First, make sure that your
+regression config file uses the same catalog backend as your installed
+binaries.  Then define the variables bin and scripts variables in your config
+file.
+
+Example:
+bin=/opt/bacula/bin
+scripts=/opt/bacula/scripts
+
+The ./scripts/prepare-other-loc will tweak the regress scripts to use
+your binary location. You will need to run it manually once before you run any
+regression tests.
+
+$ ./scripts/prepare-other-loc
+$ ./tests/backup-bacula-test
+...
+
+All regression scripts must be run by hand or by calling the test scripts.  
+These are principally scripts that begin with all_... such as all_disk_tests},
+./all_tests
+
+None of the 
+./do_disk, ./do_all, ./nightly...  scripts will work.
+
+If you want to switch back to running the regression scripts from source, first
+remove the bin and scripts variables from your config file and
+rerun the make setup step.
+


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.