4 This is Bacula's regression script directory.
6 To set it up, create your personal configuration file, by
7 copying prototype.conf to xxx.conf or simply editing prototype.conf
10 Then edit your conf file and define appropriate values
11 for the variables that are in that file. If you want to see
12 a real example, look at kern.conf, but please don't use my
15 Make sure that depkgs is pre-built if it isn't
16 already: (cd your-depkgs; make sqlite).
17 Using the .conf file, you can now select between any Catalog type:
18 SQLite, SQLite3, MySQL, or PostgreSQL. Be aware, however, if you
19 use an installed database on a production server, running these
20 tests will delete all the tables !!!!!!!!!!!!!!!!!! I run my
21 tests on a non-production machine, and in addition, I normally use
22 SQLite as the database, while my production uses MySQL.
29 You run the above one time. This will build a Makefile from
30 Makefile.in and your xxx.conf file, copy the Bacula source,
31 configure, build it, and configure all the Bacula scripts
32 and conf files. If you change your source, you will need to
35 Then you can run any of the tests in the tests subdirectory.
36 Each test whose name ends in -root requires you to be root for
37 a resonable run. Each test is totally independent of any other
38 test. Aside from the required "make setup", each test is totally
39 self-initalizing and should clean up after itself.
41 Not all the tests yet report OK. This is simply because there are
42 some spurious differences that I haven't yet taken the time to
43 eliminate. The working scrips as of 24 Apr 03 are (this is
49 sparse-compressed-test
54 The tests expect you to execute them from the main regress
57 You can run all the disk based tests by doing:
61 You can run all the disk and most of the tape tests by doing:
65 Each of the above calls one or more scripts. By looking at the
66 scripts available in this directory, you can see that there are a number
67 of options for running tests.
69 You can run them individually as:
73 or all non-root tests (my normal testing under my account)
77 or all tests (I only run these before a production release):
83 after running the root tests, while still root, it is a good idea
88 this cleans up any files that may be created with root permissions.
90 If you want to add more tests, do so by putting the shell script
91 in the tests subdirectory. Be careful when adding (or better not)
92 new clients, pools, and such to the test-bacula-dir.conf.in file
93 as it may invalidate a good number of tests, which respond to
94 questions by answering with a number (i.e. the order of the selection
95 list is known). It might be better to add your own testb-bacula...
98 To avoid re-doing a make setup if you have made a change to the
99 conf files, and you do not need a new copy of the source, you can simply do:
103 Debugging failed tests:
104 The simplest thing to do is to edit tests/xxxx where xxxx is the name of
105 the test, and change the line "debug=0" to "debug=1". If the test has
106 not been updated to have the debug variable, please notify Kern, and I
107 will be happy to fix it -- I am upgrading them one at a time.