Improve Mailable assertion error messages with expected vs actual values #56221
+62
−26
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.
Currently, when mailable assertions fail, developers only see generic error messages that don't show what was actually found vs what was expected. This forces developers to dig through code to understand why tests are failing.
Changes:
assertHasSubject()
- Shows expected vs actual subjectassertFrom()
- Shows expected vs actual sender informationassertTo()
/assertHasTo()
- Shows expected vs actual recipientsassertHasCc()
- Shows expected vs actual CC recipientsassertHasBcc()
- Shows expected vs actual BCC recipientsassertHasReplyTo()
- Shows expected vs actual reply-to addressesassertHasTag()
- Shows expected tag vs actual tags listassertHasMetadata()
- Shows expected vs actual metadata valuesUsage: