| /dports/devel/boost-docs/boost_1_72_0/libs/test/doc/adv_scenarios/ |
| H A D | single_header_customizations.qbk | 14 * one translation unit should define __BOOST_TEST_MODULE__ and include `<boost/test/included/unit_t…
19 * Translation unit 1, defines __BOOST_TEST_MODULE__
46 … this usage variant and in the translation unit containing the definition of __BOOST_TEST_MODULE__,
58 [note The above example also illustrates that it makes sense to define both __BOOST_TEST_MODULE__ a…
59 … This way, no `main` is generated by the framework, but the name specified by __BOOST_TEST_MODULE__
70 In this usage variant, you do not define macro __BOOST_TEST_MODULE__ and instead provide the defini…
|
| H A D | test_module_init_overview.qbk | 14 …) it needs to provide the definition. You do it by defining macro __BOOST_TEST_MODULE__ in the des…
17 the value of the macro __BOOST_TEST_MODULE__.
20 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
28 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/devel/boost-python-libs/boost_1_72_0/libs/test/doc/adv_scenarios/ |
| H A D | single_header_customizations.qbk | 14 * one translation unit should define __BOOST_TEST_MODULE__ and include `<boost/test/included/unit_t…
19 * Translation unit 1, defines __BOOST_TEST_MODULE__
46 … this usage variant and in the translation unit containing the definition of __BOOST_TEST_MODULE__,
58 [note The above example also illustrates that it makes sense to define both __BOOST_TEST_MODULE__ a…
59 … This way, no `main` is generated by the framework, but the name specified by __BOOST_TEST_MODULE__
70 In this usage variant, you do not define macro __BOOST_TEST_MODULE__ and instead provide the defini…
|
| H A D | test_module_init_overview.qbk | 14 …) it needs to provide the definition. You do it by defining macro __BOOST_TEST_MODULE__ in the des…
17 the value of the macro __BOOST_TEST_MODULE__.
20 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
28 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/devel/boost-libs/boost_1_72_0/libs/test/doc/adv_scenarios/ |
| H A D | single_header_customizations.qbk | 14 * one translation unit should define __BOOST_TEST_MODULE__ and include `<boost/test/included/unit_t…
19 * Translation unit 1, defines __BOOST_TEST_MODULE__
46 … this usage variant and in the translation unit containing the definition of __BOOST_TEST_MODULE__,
58 [note The above example also illustrates that it makes sense to define both __BOOST_TEST_MODULE__ a…
59 … This way, no `main` is generated by the framework, but the name specified by __BOOST_TEST_MODULE__
70 In this usage variant, you do not define macro __BOOST_TEST_MODULE__ and instead provide the defini…
|
| H A D | test_module_init_overview.qbk | 14 …) it needs to provide the definition. You do it by defining macro __BOOST_TEST_MODULE__ in the des…
17 the value of the macro __BOOST_TEST_MODULE__.
20 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
28 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/devel/hyperscan/boost_1_75_0/libs/test/doc/adv_scenarios/ |
| H A D | single_header_customizations.qbk | 14 * one translation unit should define __BOOST_TEST_MODULE__ and include `<boost/test/included/unit_t…
19 * Translation unit 1, defines __BOOST_TEST_MODULE__
46 … this usage variant and in the translation unit containing the definition of __BOOST_TEST_MODULE__,
58 [note The above example also illustrates that it makes sense to define both __BOOST_TEST_MODULE__ a…
59 … This way, no `main` is generated by the framework, but the name specified by __BOOST_TEST_MODULE__
70 In this usage variant, you do not define macro __BOOST_TEST_MODULE__ and instead provide the defini…
|
| H A D | test_module_init_overview.qbk | 14 …) it needs to provide the definition. You do it by defining macro __BOOST_TEST_MODULE__ in the des…
17 the value of the macro __BOOST_TEST_MODULE__.
20 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
28 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/devel/boost-docs/boost_1_72_0/libs/test/doc/test_organization/ |
| H A D | master_test_suite.qbk | 69 reset the name to a different value: using the macro __BOOST_TEST_MODULE__
73 [bt_example example14..Naming master test suite using the macro __BOOST_TEST_MODULE__..run]
75 If the macro __BOOST_TEST_MODULE__ is defined, the test module initialization
81 Without the __BOOST_TEST_MAIN__ and the __BOOST_TEST_MODULE__ flags defined, the test module initia…
|
| /dports/devel/boost-libs/boost_1_72_0/libs/test/doc/test_organization/ |
| H A D | master_test_suite.qbk | 69 reset the name to a different value: using the macro __BOOST_TEST_MODULE__
73 [bt_example example14..Naming master test suite using the macro __BOOST_TEST_MODULE__..run]
75 If the macro __BOOST_TEST_MODULE__ is defined, the test module initialization
81 Without the __BOOST_TEST_MAIN__ and the __BOOST_TEST_MODULE__ flags defined, the test module initia…
|
| /dports/devel/boost-python-libs/boost_1_72_0/libs/test/doc/test_organization/ |
| H A D | master_test_suite.qbk | 69 reset the name to a different value: using the macro __BOOST_TEST_MODULE__
73 [bt_example example14..Naming master test suite using the macro __BOOST_TEST_MODULE__..run]
75 If the macro __BOOST_TEST_MODULE__ is defined, the test module initialization
81 Without the __BOOST_TEST_MAIN__ and the __BOOST_TEST_MODULE__ flags defined, the test module initia…
|
| /dports/devel/hyperscan/boost_1_75_0/libs/test/doc/test_organization/ |
| H A D | master_test_suite.qbk | 69 reset the name to a different value: using the macro __BOOST_TEST_MODULE__
73 [bt_example example14..Naming master test suite using the macro __BOOST_TEST_MODULE__..run]
75 If the macro __BOOST_TEST_MODULE__ is defined, the test module initialization
81 Without the __BOOST_TEST_MAIN__ and the __BOOST_TEST_MODULE__ flags defined, the test module initia…
|
| /dports/databases/xtrabackup/boost_1_59_0/libs/test/doc/adv_scenarios/ |
| H A D | test_module_init_overview.qbk | 10 …__BOOST_TEST_MODULE__ in the designated file. The default implementation assigns the name to the […
13 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
20 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/databases/percona57-pam-for-mysql/boost_1_59_0/libs/test/doc/adv_scenarios/ |
| H A D | test_module_init_overview.qbk | 10 …__BOOST_TEST_MODULE__ in the designated file. The default implementation assigns the name to the […
13 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
20 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/databases/mysqlwsrep57-server/boost_1_59_0/libs/test/doc/adv_scenarios/ |
| H A D | test_module_init_overview.qbk | 10 …__BOOST_TEST_MODULE__ in the designated file. The default implementation assigns the name to the […
13 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
20 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/databases/percona57-server/boost_1_59_0/libs/test/doc/adv_scenarios/ |
| H A D | test_module_init_overview.qbk | 10 …__BOOST_TEST_MODULE__ in the designated file. The default implementation assigns the name to the […
13 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
20 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/databases/percona57-client/boost_1_59_0/libs/test/doc/adv_scenarios/ |
| H A D | test_module_init_overview.qbk | 10 …__BOOST_TEST_MODULE__ in the designated file. The default implementation assigns the name to the […
13 For a test module consisting of multiple source files you have to define __BOOST_TEST_MODULE__ in a…
20 * in order to assign the custom name to the master test suite define macro __BOOST_TEST_MODULE__ to…
|
| /dports/devel/boost-python-libs/boost_1_72_0/libs/test/doc/ |
| H A D | usage_variants.qbk | 28 #define __BOOST_TEST_MODULE__ test module name
31 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should indicate
52 #define __BOOST_TEST_MODULE__ test module name
55 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should indicate the
80 #define __BOOST_TEST_MODULE__ test module name
|
| /dports/databases/mysqlwsrep57-server/boost_1_59_0/libs/test/doc/ |
| H A D | usage_variants.qbk | 28 #define __BOOST_TEST_MODULE__ test module name
31 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
53 #define __BOOST_TEST_MODULE__ test module name
56 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
81 #define __BOOST_TEST_MODULE__ test module name
|
| /dports/databases/percona57-pam-for-mysql/boost_1_59_0/libs/test/doc/ |
| H A D | usage_variants.qbk | 28 #define __BOOST_TEST_MODULE__ test module name
31 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
53 #define __BOOST_TEST_MODULE__ test module name
56 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
81 #define __BOOST_TEST_MODULE__ test module name
|
| /dports/databases/percona57-server/boost_1_59_0/libs/test/doc/ |
| H A D | usage_variants.qbk | 28 #define __BOOST_TEST_MODULE__ test module name
31 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
53 #define __BOOST_TEST_MODULE__ test module name
56 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
81 #define __BOOST_TEST_MODULE__ test module name
|
| /dports/databases/xtrabackup/boost_1_59_0/libs/test/doc/ |
| H A D | usage_variants.qbk | 28 #define __BOOST_TEST_MODULE__ test module name
31 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
53 #define __BOOST_TEST_MODULE__ test module name
56 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
81 #define __BOOST_TEST_MODULE__ test module name
|
| /dports/databases/percona57-client/boost_1_59_0/libs/test/doc/ |
| H A D | usage_variants.qbk | 28 #define __BOOST_TEST_MODULE__ test module name
31 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
53 #define __BOOST_TEST_MODULE__ test module name
56 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should be set to
81 #define __BOOST_TEST_MODULE__ test module name
|
| /dports/devel/boost-libs/boost_1_72_0/libs/test/doc/ |
| H A D | usage_variants.qbk | 28 #define __BOOST_TEST_MODULE__ test module name
31 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should indicate
52 #define __BOOST_TEST_MODULE__ test module name
55 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should indicate the
80 #define __BOOST_TEST_MODULE__ test module name
|
| /dports/devel/boost-docs/boost_1_72_0/libs/test/doc/ |
| H A D | usage_variants.qbk | 28 #define __BOOST_TEST_MODULE__ test module name
31 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should indicate
52 #define __BOOST_TEST_MODULE__ test module name
55 __BOOST_TEST_MODULE__ macro needs to be defined *before* the include and should indicate the
80 #define __BOOST_TEST_MODULE__ test module name
|