Migrating a KIF test suite to Swift 6, any known issues with strict concurrency?

[inmabarrera]

Hi everyone!

I’m starting to migrate a large project that uses KIF for UI testing to Swift 6 with strict concurrency.

As far as I understand, KIF internally manages its own runloop (CFRunLoopRunInMode), so I was wondering if anyone has encountered issues or limitations when running KIF tests in this context, especially when working with async/await code or actor-isolated dependencies.

Before diving deeper, I’d love to know:
• Are there any known incompatibilities between KIF and Swift 6’s concurrency model?
• Has anyone found a recommended approach for integrating KIF with actor-based code or async workflows?

Thanks a lot in advance.

[justinseanmartin]

I haven't heard of anyone report issues thus far, but it'd be great to hear back about your experience once you make some progress. As far as I can think of, as long as you're solely using KIF APIs to walk the UI View/Accessibility hierarchy and interact with UI elements and not directly interacting with objects owned by your app in tests, I don't see why it'd be a problem. KIF performs all test execution on the main thread on a polling interval. If you're directly interacting with objects in your app (e.g. via static variables/functions exposed in your code or UIKit, via the UIView returned by KIF actor methods like waitForView or waitForTappableView, etc), then that might be where things potentially might have issues, but I'm not sure exactly what that might look like. Good luck with the migration!