Want to refactor your SwiftUI views without worrying you'll break something? Here's the first test that makes that possible. https://qualitycoding.org/swiftui-tdd-fake-it-till-you-make-it-part-2/

In TDD, you sometimes write code that looks obviously wrong on purpose — like hard-coding "0" instead of real logic. It feels uncomfortable. That discomfort is actually the point. Here's why. https://qualitycoding.org/swiftui-tdd-fake-it-till-you-make-it-part-2/

Why I Hard-Coded "0" Into My SwiftUI View on Purpose https://qualitycoding.org/swiftui-tdd-fake-it-till-you-make-it-part-2/

SwiftUI TDD: Fake It Till You Make It (Part 2) https://qualitycoding.org/swiftui-tdd-fake-it-till-you-make-it-part-2/

New in TestableView: An easy way to unit test how Environment changes your SwiftUI views. https://github.com/jonreid/TestableView

Have you ever written a custom test assertion in Swift Testing and watched the failure point to the helper function instead of your actual test? https://qualitycoding.org/swift-testing-custom-assertions/

Discover how Swift 6's MainActor isolation impacts XCTest, with tips on handling concurrency warnings for view controller testing. https://qualitycoding.org/xctest-mainactor/

Swift Testing's failure messages look "funny". But that's not the real problem. The real problem is when they show up in the wrong place entirely. https://qualitycoding.org/swift-testing-custom-assertions/ #SwiftLang

Ahh, naming. Claude started with TipsController because hey, consider how many Controller classes it's seen. It can do better — if you know better. I called out "controller" so it went with TipsBootstrapper. But again I had that nagging thought: we can do better still.

SourceLocation: The Secret to Better Custom Assertions in Swift Testing https://qualitycoding.org/swift-testing-custom-assertions/ #SwiftTesting

Would you unit test this SwiftUI? If so, how would you do it? What parts are worth testing, and what parts aren't? How would you approach it with TDD? https://qualitycoding.org/swiftui-testing-challenge/

Custom Assertions in Swift Testing: Getting Failures in the Right Place https://qualitycoding.org/swift-testing-custom-assertions/ #iOSDevelopment

"When I visited her in the Wichita Falls jail in May, her spirits were bright despite her circumstances. I wanted to ask her about what she’s been reading, but wondered if she was scared to answer. 'It’s crazy that we live in a world where it’s not safe to ask what books you’re reading,' she said."

Struggling with a thousand-line view controller with minimal tests? Learn the legacy code rescue techniques I used on an iOS app. https://qualitycoding.org/legacy-code-rescue-thousand-line-view-controller/

My Discovery Tree skill now renders in ASCII (in addition to Mermaid) https://github.com/jonreid/DiscoveryTreeSkill

Does Spec-Driven Development replace agile? Are they actually at odds? This discussion with @iamleeg.bsky.social helped me overcome my biases. codeforthought.buzzsprout.com/1326658/epis...

Have you ever written a custom test assertion in Swift Testing and watched the failure point to the helper function instead of your actual test? https://qualitycoding.org/swift-testing-custom-assertions/ #SwiftLang

New blue paint appears to be peeling from the bottom of the Lincoln Memorial Reflecting Pool. So far the algae seems to be winning.

Swift Testing's failure messages look "funny". But that's not the real problem. The real problem is when they show up in the wrong place entirely. https://qualitycoding.org/swift-testing-custom-assertions/

SourceLocation: The Secret to Better Custom Assertions in Swift Testing https://qualitycoding.org/swift-testing-custom-assertions/

Is LinkedIn website broken for anyone else? I tried disabling my ad blockers but that hasn't helped.

How to Make Custom Test Assertions in Swift Testing https://qualitycoding.org/swift-testing-custom-assertions/

"While SLOC (source lines of code) may provide a yardstick by which to measure individual effort and application complexity, it says nothing about overall quality." — https://bsky.app/profile/sandimetz.bsky.social, POODR I'm looking at you, AI-accelerated code generation.

Overheard: someone saying “this is the beginning of the end” as they watch the completion of the scaffolding at the Kennedy Center, and a woman yelling GIVE ME A “D”! 😂

I practice AI-augmented TDD, moving in small steps. The other day, I decided to try just handing the plan to Claude and walking away while it did it all without my intervention. …Can you guess what happened?

Say, I have had custom Xcode file templates for a long time. I would ⌘N, select my template, then Xcode would prompt me for file name (which I use in my template). But now Xcode has stopped showing the file name prompt. What gives?

Just starting to watch the #WWDC keynote. Oh hey, they highlight the most egregious things about Liquid Glass that will be "improved" in iOS 27, meaning fixed. Meanwhile, here's my lovely face on iOS 26:

Does testing SwiftUI feel impossible compared to writing the feature itself? https://qualitycoding.org/swiftui-tdd-first-failing-test-part-1/

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/

Heavy AI-adopting teams: change failure rates +30%. Incidents per PR +23.5%. Speeding up code generation didn't speed up delivery. It just moved the queue downstream into review and incidents.

🙈 You wouldn't ship backend code without tests. Why are we shipping SwiftUI without unit tests? Let's fix that. https://qualitycoding.org/swiftui-tdd-first-failing-test-part-1/

Released new version of Discovery Tree skill. Thanks to @garyash.bsky.social for the contributions! github.com/jonreid/Disc...

From Zero Tests to TDD: Your SwiftUI Testing Journey Starts Here 👣 https://qualitycoding.org/swiftui-tdd-first-failing-test-part-1/

As I set AI loose on a refactoring, I remind it: "move in small steps running tests frequently"

Just in case you thought anti-trans rhetoric was just about women’s toilets and competition in sports.

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/

🧪 TDD + ViewInspector: Writing Your First Failing SwiftUI Test https://qualitycoding.org/swiftui-tdd-first-failing-test-part-1/

"Intro to Test-Driven Development" https://www.youtube.com/watch?v=xlHU9vhYX60

Does testing SwiftUI feel impossible compared to writing the feature itself? https://qualitycoding.org/swiftui-tdd-first-failing-test-part-1/

🙈 You wouldn't ship backend code without tests. Why are we shipping SwiftUI without unit tests? Let's fix that. https://qualitycoding.org/swiftui-tdd-first-failing-test-part-1/

From Zero Tests to TDD: Your SwiftUI Testing Journey Starts Here 👣 https://qualitycoding.org/swiftui-tdd-first-failing-test-part-1/

SwiftUI TDD: Writing Your First Failing Test (Part 1) | Quality Coding https://qualitycoding.org/swiftui-tdd-first-failing-test-part-1/

Mocks often make unit tests easier to write. But how do we mock, when Swift is strict about types? The trick is to use Swift's protocols and extensions. https://qualitycoding.org/swift-mocking/

This book by David Tanzer highlights various technical agile practices, much like a restaurant menu. Read an entry in just a few minutes to learn where you want to go deeper. https://qualitycoding.org/agile-engineering-practices-book/

Tired of relying on SwiftUI Previews for testing? ViewInspector unlocks real unit tests. https://qualitycoding.org/viewinspector-risks-benefits/

Third-party tools aren't ideal—but they're essential. Apple's never solved SwiftUI testing. The community has. Meet ViewInspector. https://qualitycoding.org/viewinspector-risks-benefits/

Previews Aren't Enough: Why SwiftUI Testing Needs Automation https://qualitycoding.org/viewinspector-risks-benefits/

Watching Vance and Johnson try to school the Pope is an exercise in hilarity.

"Test Driven Development for iOS (and anything)" TDD seems like a good idea... for simple code that has no dependencies! But for iOS we do a lot of networking and UI... you may think that TDD just doesn't work in such cases. But that's just not so! https://www.youtube.com/watch?v=Jzlz3Bx-NzM