[6.x] Throw exception on empty collection #31471
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.
When someone passes an empty collection of notifiables to the
assertSentTo
orassertNotSentTo
methods of aNotificationFake
then the test will be marked as risky because no assertions were made. It seems to me that if you want to perform the assertion that you'd always want to make sure that you're passing at least one notifiable. Throwing an exception on an empty collection will make it more obvious why the test isn't run.Fixes #31459