-
-
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
Add custom failure messages with lazy stringification #23
Comments
this is planned - it is in the roadmap - Currently I don't see how to implement this without always constructing the strings - even when the assertions pass. |
This is implemented in the dev branch - check out the documentation |
… from an exception - relates #48 #23 (also see this Catch PR: catchorg/Catch2#876 )
… from an exception - relates #48 #23 (also see this Catch PR: catchorg/Catch2#876 )
Is it or will it possible to output custom messages only when
REQUIRE
orCHECK
fails? In Catch, we can capture certain variables before doing the check, but that unnecessarily creates a string and then discards it when the test succeeds (which should be more common than failures).The text was updated successfully, but these errors were encountered: