diff options
Diffstat (limited to 'qpid/cpp/src/tests/README.txt')
| -rw-r--r-- | qpid/cpp/src/tests/README.txt | 51 |
1 files changed, 17 insertions, 34 deletions
diff --git a/qpid/cpp/src/tests/README.txt b/qpid/cpp/src/tests/README.txt index 0f4edee493..8eaa5bbd25 100644 --- a/qpid/cpp/src/tests/README.txt +++ b/qpid/cpp/src/tests/README.txt @@ -1,54 +1,37 @@ = Running Qpid C++ tests = -General philosophy is that "make check" run all tests by default, but +General philosophy is that "make test" run all tests by default, but developers can run tests selectively as explained below. -== Valgrind == - -By default we run tests under valgrind to detect memory errors if valgrind -is present. ./configure --disable-valgrind will disable it. - -Default valgrind options are specified in .valgrindrc-default, which a -checked-in file. The actual options used are in .valgrindrc which is a -local file. Normally it is a copy of valgrindrc-default but you can -modify at will. - -Supressed errors are listed in .valgrind.supp. If you want to change -suppressions for local testing, just modify .valgrindrc to point to a -different file. Do NOT add suppressions to .valgrindrc.supp unless -they are known problems outside of Qpid that can't reasonably be -worked around in Qpid. - - == Unit Tests == -Unit tests use the boost test framework, and are compiled to rogram - unit_test -There are several options to control how test results are displayed, -see - http://www.boost.org/doc/libs/1_35_0/libs/test/doc/components/utf/parameters/index.html -NOTE: some unit tests are written as CppUnit plug-ins, we are moving away -from CppUnit so new tests should use the boost framework. +Unit tests use the boost test framework, and are compiled to the programd +unit_test -CppUnit tests are run by the script run-unit-tests. +There are several options to control how test results are displayed, see + http://www.boost.org/doc/libs/1_35_0/libs/test/doc/components/utf/parameters/index.html == System Tests == -System tests are self contained AMQP client executables or scripts. -They are listed in the TESTS make variable, which can be over-ridden. - -The ./start_broker "test" launches the broker, ./stop_broker" stops it. -Tests in between assume the broker is running. +System tests are executables or scripts. You can run executable tests directly +as well as via "make test" or "ctest". Some tests require environment settings +which are set by src/tests/test_env.sh on Unix or by src/tests/test_env.ps1 on +Windows. ./python_tests: runs ../python/run_tests. This is the main set of -system testss for the broker. +system tests for the broker. Other C++ client test executables and scripts under client/test are system tests for the client. -By setting TESTS in a make command you can run a different subset of tests -against an already-running broker. +== Running selected tests == +The make target "make test" simply runs the command "ctest". Running ctest +directly gives you additional options, e.g. + ctest -R <regexp> -VV +This runs tests with names matching the regular expression <regexp> and will +print the full output of the tests rather than just listing which tests pass or +fail. |