We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some (most) assertion failures give strange "reason" messages. Example:
$this->Assert(false)->Should()->NotBeFalse();
fails for reason: Failed asserting that false is true
Failed asserting that false is true
The reason should be: Failed asserting that false is not false
Failed asserting that false is not false
As a sidenote to this, the assertions should throw custom exceptions instead of calling PHPUnit's base asserter.
Example failure message
FluentAssertionException: expected true to be false because false is falsey"
(Custom reason provided starting at because)
because
The text was updated successfully, but these errors were encountered:
Throwing exceptions also allows us to do internal reverse testing.
We'll be able to check that a test fails instead of trying to test every other possible combination.
Sorry, something went wrong.
nevadascout
No branches or pull requests
Some (most) assertion failures give strange "reason" messages. Example:
fails for reason:
Failed asserting that false is true
The reason should be:
Failed asserting that false is not false
As a sidenote to this, the assertions should throw custom exceptions instead of calling PHPUnit's base asserter.
Example failure message
(Custom reason provided starting at
because
)The text was updated successfully, but these errors were encountered: