Rachel Brindle
Rachel Brindle
Read the full proposal [here](https://github.com/younata/swift-testing/blob/proposal/third-party-issue-recording/Documentation/Proposals/NNNN-third-party-issues.md) ### Motivation: To improve the experience of users using third party assertion tools, we should improve the API for recording Issues so that assertion failures...
### Description I'm in the process of creating a BDD-style DSL on top of Swift Testing (https://github.com/Quick/Quick/pull/1292), and I'm looking at creating `Testing.Test`s. I could use [`Testing.Test.__function`](https://github.com/apple/swift-testing/blob/main/Sources/Testing/Test%2BMacro.swift#L408-L433), but that's explicitly...
### Description Just discussed in a lab. To better facilitate integrate with third party assertion tools, there should be a dedicated `Issue.Kind` case for them. Because the current `expectationFailed` takes...
### Description This is something I learned while researching potential ways to address #475. Which, at the time I wrote that issue, I thought would have just resulted in the...
It would be nice to have a way to a beforeEach that runs before the beforeEachs defined earlier than the other beforeEachs in a test. Something like this: ```swift beforeEach...
Swift Testing is the new, mostly open source testing framework for Swift. It provides a pytest-style approach to testing, with native support for nested tests, like what Quick and other...
Fixes https://github.com/Quick/Quick/issues/1298 https://github.com/Quick/Quick/pull/1289, which seemed like good idea at the time, ended up breaking standard specs when building under strict concurrency. This will reintroduce build errors of type "Main actor-isolated...
The PR should summarize what was changed and why. Here are some questions to help you if you're not sure: - What behavior was changed? - What code was refactored...
Protocols can't be extended to conform to other protocols, sadly. So this duplicates the haveValidSnapshot/recordSnapshot matchers with ones that take in a SwiftUI View. Then, inside of that, the SwiftUI...