[9.x] Add NotificationFake::assertNothingSentTo() #41232
Merged
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.
Right now there is no easy way to assert that no notifications have been sent to a specific notifiable. Laravel does allow you to assert that no notifications have been sent at all, but this isn't always applicable.
This is primarily an issue when a piece of code dispatches various notification types to different notifiables, for example:
The example above is quite simple and only sends 2 notifications, but the number of calls to
assertNotSentTo
would increase by one for every additional notification type that is dispatched.This PR aims to simplify testing in these kinds of scenario's by adding
Notification::assertNothingSentTo($notifiable)
PS. This PR includes a test for
NotificationFake::assertNothingSent()
, which appeared to be missing