1
0
mirror of https://github.com/samba-team/samba.git synced 2025-01-12 09:18:10 +03:00
samba-mirror/ctdb/tests/eventscripts
Martin Schwenke e4ba51effd Tests - eventscripts - remove undefined argument in some simple_test calls
Signed-off-by: Martin Schwenke <martin@meltin.net>

(This used to be ctdb commit c490024aba39cf94cbc9f8f41ecb3d336b1c82a8)
2011-08-30 16:51:55 +10:00
..
etc Tests - evenscripts - add symlink to ctdb.sysconfig 2011-08-30 16:51:55 +10:00
etc-ctdb Tests: initial eventscript unit tests. 2011-08-08 13:38:07 +10:00
simple Tests - eventscripts - remove undefined argument in some simple_test calls 2011-08-30 16:51:55 +10:00
stubs Tests - eventscripts - nmap and netstat stubs can pretend they weren't found 2011-08-30 16:51:55 +10:00
common.sh Tests - eventscripts - add a new ctdb_not_implemented() function 2011-08-30 16:51:55 +10:00
README Tests: initial eventscript unit tests. 2011-08-08 13:38:07 +10:00
run_tests.sh Tests - add -T (trace) option to eventscripts run_test.sh 2011-08-30 16:51:54 +10:00

eventscript unit tests
======================

This directory contains some eventscript unit tests for CTDB.  These
tests can be run as a non-privileged user.  There are a lot of stub
implementations of commands (located in bin/) used to make the
eventscripts think they're running against a real system.

Examples:

* ./run_tests.sh

  Run all tests, displaying minimal output.

* ./run_tests.sh -s

  Run all tests, displaying minimal output and a summary.

* ./run_tests.sh  -s simple/*.sh

  Run all the tests in the simple/ subdirectory.

* ./run_tests.sh -v -s

  Run all tests, displaying extra output and a summary.

* ./run_tests.sh -sq

  Run all tests, displaying only a summary.

* EVENTSCRIPTS_TESTS_TRACE="sh -x" \
    ./run_tests.sh simple/10.interface.startup.002.sh

  Run a test and have the eventscript itself run with "sh -x".  This
  will usually make a test fail because the (undesirable) trace output
  will be included with the output of the eventscript.  However, this
  is useful for finding out why a test might be failing.  You can just
  drop the "-x" (minimal command-line editing) to see if changes have
  made a test pass.

The simple/ subdirectory contains tests that exercise only a single
eventscript.  Another directory containing tests that exercise
interactions between eventscripts is coming soon...  :-)