-
-
Notifications
You must be signed in to change notification settings - Fork 649
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
!!! BREAKING CHANGE !!! - Make TEST_SUITE work with blocks and add TEST_SUITE_BEGIN #41
Comments
having For allowing test suites to have bodies and test cases inside them - not sure how that could be implemented - but one thing is for sure - the I'll have to think about these things... |
Actually this is possible! - see UnitTest++ The only drawback is that it will be a breaking change but I don't think test suites are used that much given that the framework is not that known yet - will document it in the changelog as a breaking change. |
TEST_SUITE
work with bodies, add TEST_SUITE_BEGIN
This is how test suites are used now (in the dev branch - not yet released): TEST_CASE("") {} // not part of any test suite
TEST_SUITE("math") {
TEST_CASE("") {} // part of the math test suite
TEST_CASE("") {} // part of the math test suite
}
TEST_SUITE_BEGIN("utils");
TEST_CASE("") {} // part of the utils test suite
TEST_SUITE_END();
TEST_CASE("") {} // not part of any test suite |
Nevermind :) |
I figured out how to circumvent the string literal issue - and even edited my comment from 2 hours ago. This is already implemented in the dev branch! I too like the new unified way of calling |
Sorry, I had the page open for a while before submitting my comment, so I didn't catch that. Nice work! |
I think making the following code valid would be a good idea
and adding the macro/typedef
TEST_SUITE_BEGIN
, to matchTEST_SUITE_END
The text was updated successfully, but these errors were encountered: