StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
963890
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-06-08T08:26:28.150
FavoriteCount
0
LastActivityDate
2009-06-08T08:26:28.150
LastEditDate
LastEditorUserId
0
OwnerUserId
115259
ParentId
963158
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
In your <code>test_foo.cpp</code>, the macros add test suites and test cases in to a global list: <code>master_testsuite</code>, which is the root of all test nodes. You just need to compile all the test files like <code>test_foo.cpp</code>, <code>test_boo.cpp</code> and a runner, then link them all into on executable. The function <code>unit_test_main</code> is used to run the tests in <code>master_testsuite</code>. <pre><code>boost::unit_test::unit_test_main( &init_unit_test, argc, argv ) </code></pre> Based on the macro you defined before including <code><boost/test/unit_test.h></code>, Boost.Test may already generate the <code>main</code> function for you.[1] The generated <code>main</code> simply invoked <code>unit_test_main</code> with <code>argc</code> and <code>argv</code> in <code>main</code>. It's recommended to use <code>unit_test_main</code> because it can process some console arguments, like <a href="http://www.boost.org/doc/libs/1_39_0/libs/test/doc/html/utf/user-guide/runtime-config/run-by-name.html" rel="noreferrer" title="Running Boost Test By Name">run test by name</a>. The first argument of <code>unit_test_main</code> is a hook. Depending on <code>BOOST_TEST_ALTERNATIVE_INIT_API</code>, it has different definition. <pre><code>#ifdef BOOST_TEST_ALTERNATIVE_INIT_API typedef bool (*init_unit_test_func)(); #else typedef test_suite* (*init_unit_test_func)( int, char* [] ); #endif </code></pre> You can customize the <code>master_testsuite</code> in the hook. In the second form, the returned value is the new master testsuite. [1] if <code>BOOST_TEST_MAIN</code> and <code>BOOST_TEST_MAIN</code> are defined, but <code>BOOST_TEST_NO_MAIN</code> is not.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHelping getting started using Boost.Test
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USIan Yang
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.