You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Distinguish when an error is part of a recorded issue in an exit test. (#718)
Hot on the heels of #697…
If an exit test records an issue of kind `.errorCaught()`, we currently
treat it the same as any other issue and translate it to a flat
`.unconditional` issue in the parent process:
```swift
await #expect(exitsWith: .failure) {
Issue.record(NoSuchWeaselError()) // unconditional issue recorded
}
```
This PR distinguishes the `.errorCaught` issue kind and records an
`.errorCaught` issue in the parent process. Fidelity of errors across a
process boundary is weak, but we encode a minimal representation of the
error that should be good enough for most uses. If you need
`withKnownIssue()`, or `#expect(throws:)`, you can call them _inside_
the exit test.
### Checklist:
- [x] Code and documentation should follow the style of the [Style
Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md).
- [x] If public symbols are renamed or modified, DocC references should
be updated.
0 commit comments