Add example for how to test any error is thrown in the error testing documentation article #853
+16
−0
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
…hat_ error is thrown
heckj
requested review from
stmontgomery,
grynspan,
dennisweissmann,
briancroom,
SeanROlszewski and
suzannaratcliff
as code owners
heckj
changed the title
grynspan
changed the title
grynspan
added
documentation
|
@iamleeg Can you review? |
Sources/Testing/Testing.docc/testing-for-errors-in-swift-code.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Stuart Montgomery <[email protected]>
stmontgomery
approved these changes
Dec 12, 2024
There was a problem hiding this comment.
Looks good to me. Approving, but I'll wait a little longer to give @iamleeg an opportunity to review before merging
iamleeg
approved these changes
Dec 13, 2024
stmontgomery
approved these changes
Dec 13, 2024
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.
I was stumped earlier when trying to find the details for how to test that any error is thrown. This detail is in the migrating from XCTest content, but I landed on this page, and it seemed an odd miss, especially given the history of ignoring the kind of error in many cases. (I found my solution in a post by Jonathan the forums.)
While it is duplicated content, this would have helped me - so I'm proposing it for a documentation update. Happy to edit as y'all see fit.