Skip to content
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

Merged
merged 2 commits into from
Apr 5, 2018

Conversation

klausspanderen
Copy link
Contributor

@klausspanderen klausspanderen commented Apr 2, 2018

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.

(i *LENGTH(oneDataValues))/nTestCases,
((i+1)*LENGTH(oneDataValues))/nTestCases)));
}
#define N_TEST_CASES 5
Copy link
Owner

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.

Copy link
Contributor Author

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.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, thanks.

Copy link
Owner

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.)

@lballabio lballabio added this to the 1.13 release milestone Apr 4, 2018
lballabio pushed a commit that referenced this pull request Apr 5, 2018
@lballabio lballabio merged commit f265aa6 into lballabio:master Apr 5, 2018
lballabio added a commit that referenced this pull request Apr 5, 2018
@klausspanderen klausspanderen deleted the boost_1_67 branch April 17, 2018 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants