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).
Then do:
- ./config xxx.conf
make setup
You run the above one time. This will build a Makefile from
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
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
this cleans up any files that may be created with root permissions.
+Tape test naming convention:
+
+The last part of the tape test name indicates (in general) what kind
+of test it is. They are broken (for the most part) into test names
+ending with:
+
+ -test => a disk based test
+ -tape => a tape based test (can be a standalone tape drive
+ or an autochanger). Only one tape will be used
+ and it is assumed to be mounted.
+ -changer => you have an 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
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: