-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boost 1.67 (beta 1) does not allow to register the same test case name multiple times #446
Conversation
(i *LENGTH(oneDataValues))/nTestCases, | ||
((i+1)*LENGTH(oneDataValues))/nTestCases))); | ||
} | ||
#define N_TEST_CASES 5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was the problem here? Just curious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with the upcoming boost_1_67 release it is no longer possible that two test cases have the same name.
If no name is provided boost more or less takes the method name as internal test case name and due to the usage of boost::bind here all test cases within the for loop got the same internal name.
This changes with the usage of the preprocessor for loop. I was also considering to remove the test case split here and to get back to the old solution where we have had one test case running for multiple minutes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(And it's ok to keep the test cases split.)
multiple times. Backported from #446.
Change log Boost.Test v3.7 / boost 1.67:
Breaking changes: Adding test cases with the same name to the same test suite is reported as an error. This impacts template and parametrized test cases, as well as manually registered tests. Make sure you have no duplicate names.