]>
Commit | Line | Data |
---|---|---|
7c673cae FG |
1 | [/ |
2 | / Copyright (c) 2003 Boost.Test contributors | |
3 | / | |
4 | / Distributed under the Boost Software License, Version 1.0. (See accompanying | |
5 | / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) | |
6 | /] | |
7 | ||
8 | [section:external_test_runner The external test runner usage variant] | |
9 | ||
10 | This usage variant does not provide any [link boost_test.adv_scenarios.test_module_runner_overview test runner]. | |
11 | You employ it when you only want to define a [link ref_test_tree test tree] and possibly an | |
12 | [link boost_test.adv_scenarios.test_module_init_overview initialization function], | |
13 | and expect another (external) program to evaluate these tests. This external program will come with its own test runner. | |
14 | ||
15 | If you plan to use an external test runner with your test module, you need to build it as a dynamic library. | |
16 | You need to define macro flag __BOOST_TEST_DYN_LINK__ either in a makefile or before the header | |
17 | `boost/test/unit_test.hpp` inclusion. An external test runner utility is required to link with dynamic library. | |
18 | ||
19 | The __UTF__ comes with an example external test runner `console_test_runner`: | |
20 | Given a name of the test module (implemented as a shared library), and a name of the initialization function defined therein, | |
21 | the program can run all the tests from the module's test tree. | |
22 | ||
23 | [endsect] [/section:external_test_runner] |