Upgrade Nimble... or replace in favor of Swift Testing?

[mokagio]

Yesterday, I wanted to replace an XCTNSPredicateExpectation usage with a faster Nimble toEventually matcher but I run into some issues adding Nimble to the UITestsFoundation framework via CocoaPods.

This seems like the perfect occasion to:

• Use SPM to fetch Nimble, in line with out intention to progressively adopt SPM in favor of CocoaPods
• Upgrade Nimble to version 10.x
• Link Nimble in all the tests targets
• Replace all XCTNSPredicateExpectation expectations with Nimble's toEventually #19080

---

Update 2024/11 – I updated the issue title to "Upgrade Nimble... or replace in favor of Swift Testing?" I love Nimble and I think it offers much better API for async code testing than XCTest. But how does it stack against Swift Testing? Would it make sense to invest in adopting Swift Testing (which can run alongside XCTest) and drop Nimble? Would any of the code we assert using Nimble need to be updated as well (e.g. to use async?) to ease the migration?

[dangermattic]

Thanks for reporting! 👍

[kean]

Would it make sense to invest in adopting Swift Testing (which can run alongside XCTest) and drop Nimble?

I think it's safe to say that Swift Testing is the way to go. I've started using it the new modules.