Swift

A broad withKnownIssue wrapper treated missing snapshots as expected failures. Narrow the matcher, then prove a wrong rendered state fails.

Replacing a shared timer left an older Swift task running. Give each operation its own cancellation deadline, and test the waiter with a stalled fetch.

A global opaque UINavigationBar appearance covered a SwiftUI large title while accessibility checks passed. Remove the screen-level global write.

A serialized Swift Testing suite lost files to another suite's initializer. Inject startup cleanup so ordinary test construction leaves shared files alone.

A polling test helper failed with "ContinuousClock.now < deadline" only when its target ran in parallel. Snapshot suites held the main actor, so the wait got 3 to 5 turns in 5 seconds. A 60-second timeout would have hidden it. A turn budget fixed it, and a mutation showed that a real hang still fails within 5 seconds.

A SwiftUI screen suite recorded with swift-snapshot-testing at precision: 0.99 stayed green after the row's location text was deliberately wired to the wrong value. On a full device frame, 1% of the pixels is about 30,000, and the wrong text changed about 900. Measuring the mutation and setting precision to 0.9999 turned four of the seven cases red.

An app-hosted iOS test target passed in the console and failed in fastlane. The host app's own login screen made a network request at launch, and its response reached an unimplemented swift-dependencies test value after the tests had started. The failure belonged to no test and was visible only in the result bundle.

A macOS FSKit extension mounted from the command line could stat its source folder but not read it. The extension sandbox was denying file-read-data on a plain path. Reinstalling the app then switched the module off in a way pluginkit does not undo.

A teardown injected during login defeated a one-time wait. An exclusion gate fixed the reproduction; the production trigger remained unknown.