boost/test
2
0
Fork 0
mirror of https://github.com/boostorg/test.git synced 2026-01-25 06:42:22 +00:00
Code Issues Projects Releases Wiki Activity

new section and cross-ref

Browse Source
This commit is contained in:
Raffi Enficiaud
2014-03-10 14:16:04 +01:00
parent 30c612e324
commit 289905c7ee
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
doc/v2/test.qbk
View File

@@ -45,6 +45,7 @@
[/ content in the test organization]
[def __section_test_organization__ [link boost_test.tests_organization tests organization]]
[def __section_expected_failures__ [link boost_test.tests_organization.test_organization_test_suite.test_suite_expected_failure expected failures]]
[def __section_test_suite__ [link boost_test.tests_organization.test_organization_test_suite test suite]]
[def __section_master_test_suite__ [link boost_test.tests_organization.test_organization_test_suite.master_test_suite Master Test Suite]]
[def __testing_tools__ [link boost_test.testing_tools testing tools]]

5
doc/v2/utf.user-guide.test-organization.qbk
View File

@@ -12,11 +12,10 @@ disadvantages in single test function approach:
* No way to perform only checks for a particular subsystem of the tested unit.
* No summary of how different subsystems of the tested unit performed under in the test.
The above points should make it clear that it's preferable to split [*test module] into smaller units.
The above points should make it clear that it's preferable to split [link ref_test_module test module] into smaller units.
These units are [link boost_test.tests_organization.test_cases test cases].
To solve test tree creation problem the __UTF__ provides facilities for
[*test suite creation].
To solve test tree creation problem the __UTF__ provides facilities for __section_test_suite__ creation.