[5.7] allow 'assertJsonMissingValidationErrors' to be called without an argument #27176
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a different implementation of #27172
This PR makes calling
assertJsonMissingValidationErrors
without an argument behave the same as asassertSessionHasNoErrors()
(but it works for Json responses, since they don't store their errors in session).Example:
If this test has validation errors, it will print them to the console. If you would write the same test without the
assertJsonMissingValidationErrors()
, and then you get validation errors, the test will only print an unhelpful "expected status 201 but received 422".