You’ve dealt with flaky UI-related logic. Did Swift Testing change anything there?

Swift Testing doesn't wait for UI update cycles the way XCTest sometimes did, causing tests to race ahead and produce inconsistent results. The fix is separating UI triggers from logic validation — test the logic directly rather than through UI side effects. This architectural split between UI concerns and business logic is what makes tests stable under Swift Testing's execution model.