blob: 8eaa5bbd255faa4834363d50fe608c2dea5fbae0 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
= Running Qpid C++ tests =
General philosophy is that "make test" run all tests by default, but
developers can run tests selectively as explained below.
== Unit Tests ==
Unit tests use the boost test framework, and are compiled to the programd
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
== System Tests ==
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 tests for the broker.
Other C++ client test executables and scripts under client/test are
system tests for the client.
== 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.
|
