-
Notifications
You must be signed in to change notification settings - Fork 11.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[11.x] Introduces Exceptions
facade
#50704
Merged
Merged
Conversation
This file contains 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
❤️ |
timacdonald
reviewed
Mar 26, 2024
Co-authored-by: Tim MacDonald <[email protected]>
Co-authored-by: Tim MacDonald <[email protected]>
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.
This pull request introduces a new
Exceptions
facade to provide a consistent way to test exceptions in Laravel applications. Here is the list of methods that theExceptions
facade provides:All the examples below assume the following route:
assertReported
methodThe
assertReported
method allows you to assert that an exception was reported:assertReportedCount
methodThe
assertReportedCount
method allows you to assert the number of exceptions reported:assertNotReported
methodThe
assertNotReported
method allows you to assert that an exception was not reported:assertNothingReported
methodThe
assertNothingReported
method allows you to assert that no exceptions were reported:Optionally, you may specify a list of exceptions you wish to capture:
throwOnReport
methodThe
throwOnReport
method allows you to throw any reported exceptions:Optionally, you may specify a list of exceptions you wish to capture:
throwFirstReported
methodThe
throwFirstReported
method allows you to throw the previous reported exceptions:Optionally, you may specify a list of exceptions you wish to capture: