IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
This function is used to run a extra command to check a result. This
command is usually a script (often a stub) or an external command, so
no need to trace it with valgrind or whatever else might be specified.
In the worst case the command being run is a shell function, which
valgrind won't be able to find.
There is little use running the event script tests under valgrind.
However, when the whole test suite is being run under valgrind then it
should work.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
Autobuild-User(master): Amitay Isaacs <amitay@samba.org>
Autobuild-Date(master): Mon Sep 3 14:04:00 CEST 2018 on sn-devel-144
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 stubs/) used to make the
eventscripts think they're running against a real system.
Test case filenames look like:
<eventscript>.<event>.NNN.sh
The test helper functions will run <eventscript> with specified
options. If using the simple_test() helper function then the 1st
<event> argument is automatically passed. When simple_test_event() is
used the event name must be explicitly passed as the 1st argument -
this is more flexible and supports multiple events per test.
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 ./10.interface.*.sh
Run all the tests against the 10.interface eventscript.
* ../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.
* ../run_tests.sh -X ./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.
30eb28818d