4 This directory contains some eventscript unit tests for CTDB. These
5 tests can be run as a non-privileged user. There are a lot of stub
6 implementations of commands (located in stubs/) used to make the
7 eventscripts think they're running against a real system.
9 Test case filenames look like:
11 <eventscript>.<event>.NNN.sh
13 The test helper functions will run <eventscript> with specified
14 options. If using the simple_test() or iterate_test() helper
15 functions then the 1st <event> argument is automatically passed. When
16 simple_test_event() is used the event name must be explicitly passed
17 as the 1st argument - this is more flexible and supports multiple
24 Run all tests, displaying minimal output.
26 * ../run_tests.sh -s .
28 Run all tests, displaying minimal output and a summary.
30 * ../run_tests.sh -s ./10.interface.*.sh
32 Run all the tests against the 10.interface eventscript.
34 * ../run_tests.sh -v -s .
36 Run all tests, displaying extra output and a summary.
38 * ../run_tests.sh -sq .
40 Run all tests, displaying only a summary.
42 * ../run_tests.sh -X ./10.interface.startup.002.sh
44 Run a test and have the eventscript itself run with "sh -x". This
45 will usually make a test fail because the (undesirable) trace output
46 will be included with the output of the eventscript. However, this
47 is useful for finding out why a test might be failing.