-
-
Notifications
You must be signed in to change notification settings - Fork 29
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 third optional parameter on asserts #77
Comments
This is already for assertEquals. Or on which functions do you mean? |
@Chemaclass In fact, this functionality was implemented at the beginning but the other way around. What it did was allow you to customize the success message of the assert and not the failure one. When we changed so that success messages were for the tests and not for the asserts, it was lost. |
I also wanted this, and went to look at what it would take to implement it. Isn't it mostly done? Nearly all the
so, for example, passing a third argument to As far as I can tell, only the array and snapshot assertions are missing it. |
Yes and no @apotterri , what is implemented right now changes the name of the test when it fails, what should be modified is the reason for the error. So, in reality, even though all the assertions have 'something similar to what we want', it is actually not working at all as we want. |
Ah, ok, I see. Thanks. |
Add 3º parameter optional that will override the error message Ex.: phpunit
The text was updated successfully, but these errors were encountered: