[12.x] Improve Testing Mailable Content section #10617
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR improves the clarity and flow of the "Testing Mailable Content" section in the documentation by:
Removing the list of available assertion methods to reduce redundancy, since all relevant assertions are demonstrated directly in the example.
Adding examples for
assertDontSeeInHtml()andassertDontSeeInText()to show how to test that specific content does not appear in the mailable.Removing a duplicated example of
assertSeeInHtml()to avoid repetition.Moving the explanatory paragraph ("As you might expect...") after the code example for a more natural and logical reading flow.
These changes help make the section more focused and instructional.
Rework of: #10615 and sorry for split up the tabs.