#XCTest
Ready to move from XCTest to Swift Testing? 🧪

Learn how to migrate your existing tests to Apple’s modern testing framework and see how Xcode 27’s agentic coding tools can help.

Read the tutorial 👇
https://www.kodeco.com/53560697-moving-from-xctest-to-swift-testing
September 16, 2026 at 3:03 PM
📊 𝑆𝑤𝑖𝑓𝑡 𝑇𝑒𝑠𝑡𝑖𝑛𝑔 𝑒𝑥𝑝𝑙𝑎𝑖𝑛𝑒𝑑 𝑤𝑖𝑡ℎ 𝑐𝑜𝑑𝑒 𝑒𝑥𝑎𝑚𝑝𝑙𝑒𝑠 by Antoine van der Lee (@avanderlee.com)

Swift Testing is settling in as the default path, and the migration story is getting clearer: @𝑇𝑒𝑠𝑡, #𝑒𝑥𝑝𝑒𝑐𝑡…

#iOSDev #Testing #Performance

www.avanderlee.com/swift-testin...
Swift Testing explained with code examples
Swift Testing is settling in as the default path, and the migration story is getting clearer: `@Test`, `#expect`, `#require`, parameterized tests, attachments, and exit tests where the platform allows them. The big win is not just fewer assertion names to remember; failure output is closer to the expression we actually wrote, which helps when CI is yelling and coffee has not kicked in yet. XCTest still has a place for UI automation and performance work, so no need for a dramatic rewrite. But for most unit tests in our codebase, the modern shape is hard to argue against.
www.avanderlee.com
September 16, 2026 at 6:01 AM
My good friend, and all-round smart guy Chris Kolbu has been working on a novel, macro-driven testing library called Exhaust that has just hit version 1.0.

He gave a really interesting talk about it at #devworld a couple of weeks back, and I'll link that video when it's available, but until then:
Exhaust: Cross-platform property-based testing, stateful testing and fuzzing
Exhaust is a feature-rich, macro-driven testing library that works with both Swift Testing and XCTest. Its aim is to empower you to test the values you didn't think of. It is the library I've wanted to have in Swift for years, ever since I started using SwiftCheck: one that matches the ergonomics and test case reduction of Python's Hypothesis with the performance of Swift. A library where you can get started with three lines of code and scale that all the way to coverage-guided fuzzing. Exhaus...
forums.swift.org
September 7, 2026 at 11:15 PM
Are you yet using Swift Testing? Apple continued to improve the framework and I barely touch XCTest anymore. Here's an update on all…

www.avanderlee.com/swift-testin...
August 22, 2026 at 3:54 PM
XCTest って便利ー
August 22, 2026 at 12:19 PM
⚡ 𝑋𝐶𝑇𝑒𝑠𝑡 𝑀𝑒𝑒𝑡𝑠 @𝑀𝑎𝑖𝑛𝐴𝑐𝑡𝑜𝑟: 𝐻𝑜𝑤 𝑡𝑜 𝐹𝑖𝑥 𝑆𝑡𝑟𝑖𝑐𝑡 𝐶𝑜𝑛𝑐𝑢𝑟𝑟𝑒𝑛𝑐𝑦 𝑊𝑎𝑟𝑛𝑖𝑛𝑔𝑠 by Jon Reid (@qualitycoding.org)

Flipping the switch to Strict Concurrency in Swift 6 turns our test suites into a sea of warnings.

#iOSDev #Concurrency #Testing

qualitycoding.org/xctest-maina...
XCTest Meets @MainActor: How to Fix Strict Concurrency Warnings
Discover how Swift 6's @MainActor isolation impacts XCTest, with tips on handling concurrency warnings for view controller testing.
qualitycoding.org
July 16, 2026 at 4:00 AM
the XCTest @MainActor piece, was there much to unpack there? I've been fighting isolation warnings in async tests for a while and still haven't landed on a clean pattern
July 12, 2026 at 2:31 AM
📢 𝗜𝘀𝘀𝘂𝗲 𝟭𝟬𝟬 𝗶𝘀 𝗼𝘂𝘁!

Featuring:
⚡ 𝑆𝑡𝑟𝑒𝑎𝑚𝑖𝑛𝑔 𝑐ℎ𝑎𝑛𝑔𝑒𝑠 𝑂𝑏𝑠𝑒𝑟𝑣𝑎𝑡𝑖𝑜𝑛𝑠
🎨 𝐶𝑢𝑠𝑡𝑜𝑚 𝑏𝑖𝑛𝑑𝑖𝑛𝑔𝑠
🧩 𝑆𝑝𝑙𝑖𝑡𝑡𝑖𝑛𝑔 𝐿𝑎𝑟𝑔𝑒 𝑉𝑖𝑒𝑤𝑠 𝐴𝑝𝑝𝑙𝑒'𝑠 𝑤𝑎𝑦
📱 𝐶𝑢𝑠𝑡𝑜𝑚 𝑃𝑢𝑙𝑙-𝑡𝑜-𝑅𝑒𝑓𝑟𝑒𝑠ℎ
🔒 𝐿𝑖𝑡𝑡𝑙𝑒 𝑆𝑤𝑖𝑓𝑡𝑈𝐼 𝑇𝑖𝑝
🚀 𝑀𝑎𝑟𝑘 𝑐𝑜𝑛𝑡𝑒𝑛𝑡 𝑝𝑟𝑖𝑣𝑎𝑡𝑒
💡 𝑋𝐶𝑇𝑒𝑠𝑡 𝑀𝑒𝑒𝑡𝑠 @𝑀𝑎𝑖𝑛𝐴𝑐𝑡𝑜𝑟
🛠️ 𝑆𝑤𝑖𝑓𝑡𝑈𝐼 𝑓𝑢𝑛𝑐𝑡𝑖𝑜𝑛𝑎𝑙

#Swift #iOSDev

ios-newsletter.snappmobile.io/issues/2026-...
iOS Newsletter Issue 100
Hi folks,
ios-newsletter.snappmobile.io
July 11, 2026 at 7:00 PM
Discover how Swift 6's MainActor isolation impacts XCTest, with tips on handling concurrency warnings for view controller testing. https://qualitycoding.org/xctest-mainactor/
XCTest Meets @MainActor: How to Fix Strict Concurrency Warnings
Discover how Swift 6's @MainActor isolation impacts XCTest, with tips on handling concurrency warnings for view controller testing.
qualitycoding.org
July 8, 2026 at 5:58 PM
Ran into yet another case where doing things the new/currently blessed Apple Way fails because their new way doesn't actually have everything needed that the old way provided.

Tonight it's that I had to use XCTest instead of Swift Testing because I need the context to assert a macro expansion […]
Original post on scoat.es
scoat.es
July 7, 2026 at 10:32 PM
🧩 𝑆𝑤𝑖𝑓𝑡 6.4 𝐿𝑎𝑛𝑔𝑢𝑎𝑔𝑒 𝐹𝑒𝑎𝑡𝑢𝑟𝑒𝑠 & 𝑇𝑒𝑠𝑡𝑖𝑛𝑔 𝐼𝑛𝑡𝑒𝑟𝑜𝑝 by Sergio De Simone

𝑤𝑒𝑎𝑘 𝑙𝑒𝑡, ~𝑆𝑒𝑛𝑑𝑎𝑏𝑙𝑒, and Swift Testing/XCTest interop smooth out migration. Plus 𝑎𝑛𝑦𝐴𝑝𝑝𝑙𝑒𝑂𝑆 cuts availability boilerplate.

#Swift #Testing #iOSDev

www.infoq.com/news/2026/06...
Swift 6.4 Brings New Language Features and Swift Testing/XCTest Interop
Currently available as a beta in Xcode 27, Swift 6.4 introduces a range of enhancements: better C interoperability, simplified OS availability check, fine-grained warning control, async support in…
www.infoq.com
July 7, 2026 at 3:03 PM
#Swift 6.4 is here! The latest release brings improvements & performance boosts:
• Up to 4× faster URL parsing
• Better C interoperability
• Fine-grained warning control
• Improved Swift Testing / XCTest interoperability
• and more

🔗 Dive into the full update: bit.ly/4bgrkEv

#Apple #iOS #InfoQ
July 2, 2026 at 12:34 PM
Right now I’m working on adding some introspection APIs so I can wire it up to XCTest to get real results in Xcode…
July 2, 2026 at 6:22 AM
June 30, 2026 at 6:00 AM
Swift 6.4 Brings New Language Features and Swift Testing/XCTest Interop Currently available as a beta in Xcode 27, Swift 6.4 introduces a range of enhancements: better C interoperability, simplifie...

#Mobile #Apple #iOS #Swift #MacOS #Programming #Languages […]

[Original post on infoq.com]
Original post on infoq.com
www.infoq.com
June 28, 2026 at 5:33 PM
Swift 6.4 Brings New Language Features and Swift Testing/XCTest Interop Currently available as a beta in Xcode 27, Swift 6.4 introduces a range of enhancements: better C interoperability, simplifie...

#Mobile #Apple #iOS #MacOS #Swift #Programming #Languages […]

[Original post on infoq.com]
Original post on infoq.com
www.infoq.com
June 28, 2026 at 8:28 AM
i used to work on XCTest and something i learned was that as the amount of test code exploded in a project the *harder* it could be to change anything. unless you introduce more abstractions! now you have an unbounded amount of problems understanding the implementation
June 19, 2026 at 11:33 PM
🧪 𝐻𝑜𝑤 𝑡𝑜 𝑀𝑎𝑘𝑒 𝐶𝑢𝑠𝑡𝑜𝑚 𝑇𝑒𝑠𝑡 𝐴𝑠𝑠𝑒𝑟𝑡𝑖𝑜𝑛𝑠 𝑖𝑛 𝑋𝐶𝑇𝑒𝑠𝑡 by Jon Reid (@qualitycoding.org)

Build reusable assertion helpers with #𝑓𝑖𝑙𝑒𝑃𝑎𝑡ℎ and #𝑙𝑖𝑛𝑒 for accurate failure locations and clearer diagnostics.

#Swift #Testing

qualitycoding.org/swift-test-a...
How to Make Custom Test Assertions in XCTest | Quality Coding
Custom test assertions can make your tests easier to read and write. How can you make them in Swift? Follow this example to learn the simple steps.
qualitycoding.org
June 4, 2026 at 6:01 AM
Apple's Swift Testing template is better than what they give us for XCTest. Now let's improve it further with a custom file template. https://qualitycoding.org/swift-testing-template/
Swift Testing Template: Download My Improved Template
Apple's Swift Testing template is better than what they give us for XCTest. Now let's improve it further with a custom file template.
qualitycoding.org
June 3, 2026 at 7:50 PM
I got curious: what if iOS UI 🛠️tests were just… a sentence?

So I built UIXCute 📦a Swift Package where you describe what you want to test in plain English, and an AI agent drives your app through XCUIAutomation until it's done.

youtu.be/BvyyRCgq2CM

#Swift #iOS #AI #XCTest
UI XCute - An SDK for agentic UI testing in Xcode.
YouTube video by Andrea Scuderi
youtu.be
May 31, 2026 at 1:21 PM
📢 𝗜𝘀𝘀𝘂𝗲 𝟵𝟰 𝗶𝘀 𝗼𝘂𝘁!

Highlights:
💡 𝑃𝑟𝑜𝑔𝑟𝑎𝑚𝑚𝑖𝑛𝑔 𝑤𝑖𝑠𝑑𝑜𝑚
🔐 𝑖𝑂𝑆 𝐾𝑒𝑦𝑐ℎ𝑎𝑖𝑛
🔢 2𝐹𝐴 𝑝𝑎𝑡𝑡𝑒𝑟𝑛 𝑠𝑝𝑜𝑡𝑡𝑖𝑛𝑔
⏱️ 𝑇𝑖𝑚𝑒𝑙𝑖𝑛𝑒𝑉𝑖𝑒𝑤
📐 𝐿𝑖𝑠𝑡 𝑟𝑜𝑤 𝑎𝑛𝑖𝑚𝑎𝑡𝑖𝑜𝑛𝑠
🍎 𝐴𝑝𝑝𝑙𝑒 𝑑𝑜𝑐𝑠 𝑓𝑜𝑟 𝐴𝐼
🧪 𝑋𝐶𝑇𝑒𝑠𝑡 𝑎𝑠𝑠𝑒𝑟𝑡𝑖𝑜𝑛𝑠
🌐 𝑀𝑖𝑛𝑖𝑆𝑤𝑖𝑓𝑡

#Swift #iOSDev

ios-newsletter.snappmobile.io/issues/2026-...
ios-newsletter.snappmobile.io
May 29, 2026 at 2:00 PM
Making custom test assertions in Swift is super easy. Follow this example to learn the simple steps to make your own. https://qualitycoding.org/swift-test-assertions/
How to Make Custom Test Assertions in XCTest | Quality Coding
Custom test assertions can make your tests easier to read and write. How can you make them in Swift? Follow this example to learn the simple steps.
qualitycoding.org
May 27, 2026 at 10:58 PM
For code I only trust answers that survive tests the model did not write. a 15 line pytest or XCTest around the edge case catches more bad output than rereading the prose. do you have your staff require a second source too, or just executable checks?
April 18, 2026 at 5:32 PM