-
Notifications
You must be signed in to change notification settings - Fork 133
BOOST_PREDICATE_MESSAGE(boolean, string message) #81
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
Comments
konserw
added a commit
to konserw/cucumber-cpp
that referenced
this issue
Aug 23, 2017
konserw
added a commit
to konserw/cucumber-cpp
that referenced
this issue
Aug 23, 2017
8 tasks
I haven't found
I believe those macros are what this issue is about. Indeed triggering those macros in code was not being detected by cucumber, but PR #164 should fix that. |
konserw
added a commit
to konserw/cucumber-cpp
that referenced
this issue
Aug 24, 2017
konserw
added a commit
to konserw/cucumber-cpp
that referenced
this issue
Aug 24, 2017
konserw
added a commit
to konserw/cucumber-cpp
that referenced
this issue
Aug 24, 2017
konserw
added a commit
to konserw/cucumber-cpp
that referenced
this issue
Sep 13, 2017
konserw
added a commit
to konserw/cucumber-cpp
that referenced
this issue
Oct 12, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using boost testing tools the messages do not show up when using the above evaluation. According to boost, if the predicate fails the custom message should appear with the failure. Instead I only receive a general message indicating failure with no string message attached. Is this a supported feature?
The text was updated successfully, but these errors were encountered: