BREAKING NEWS:
“What’s New In Testing” will begin early because Rachel Brindle has a demo ready for us! Come on over by 9:30am so you don’t miss out!
Afterwards, pop into Rachel & Dalton’s tent for the opportunity to win a copy of Daniel Steinberg’s book on Swift Testing.
First time working with the new #SwiftTesting macro.
Loving how easy it is to write tests—and how much it improves readability.
#iOSDev
Swift Testing is a new framework with expressive and intuitive APIs that improve your testing experience. It is powered by macros that allow you to organize and assert your tests. This week, we will learn about the basics of the Swift Testing framework and how we can use it side-by-side with XCTest.
#Swift #Programming #Testing #SwiftTesting
https://swiftwithmajid.com/2024/10/22/introducing-swift-testing-basics/
Stream last night went well! Even learned some more about Swift Testing and serialization.
Here's my full recap https://jaywilson.zip/posts/2025/05/01-0608-pocket-budget/
⚠️ If you’re using arguments in Swift Testing, tests run in parallel — which is great unless test order matters.
For example, if you’re using snapshots, the generated file names may depend on test order.
💡 Fix it with .serialized to ensure stable ordering:
Here's a post on making sure your SwiftTesting parameterised tests show up in the test navigator with nice names using `CustomTestStringConvertible`
https://paul-samuels.com/blog/2025/03/24/custom-test-string-convertible/
Attachments coming to Swift Testing in a review thread near you!
https://forums.swift.org/t/st-0008-exit-tests/78692
Exit tests! Death tests! Termination tests! In Swift Testing!
Just formally started the proposal process for two new Swift Testing features:
- Exit tests: https://forums.swift.org/t/pitch-exit-tests/78071
- Attachments: https://forums.swift.org/t/pitch-attachments/78072
It just hit me - because Swift Testing allows nesting of test suites, you can now have a master suite that contains a suite for testing internal implementation and a suite for testing public interface. So neat
Writing tests and improving my test coverage just helped me to find a few new issues I had, including code paths which weren't called but should have been.
Tests have saved me a lot of trouble.
I think I get more and more convinced that writing tests is very useful (still depending on the situation).
Swift Testing makes this so much easier!
We created a little app for iOS and Mac developers to make it easier to migrate Swift XCTests to the Swift Testing framework: https://furnacecreek.org/testpiler/
Does anyone know how to make it so that #Xcode doesn't totally lose its shit every time I start a #SwiftTesting test? My current workaround is I have to pick a different tab in the left sidebar and then it settles down.
While awaiting the #GluSight app review, I finally focus on rewriting unit tests with the new Swift-Testing framework. Once most are done, I’ll replace Quick & Nimble, though they did serve their purpose. I also want to reduce dependencies, and #SwiftTesting is rather elegant.
Last time, I wrote an article to introduce Swift Testing's confirmation. Are you curious about how confirmation is implemented in Swift Testing? Today's article tells you about the implementation of confirmation. #swift #swifttesting https://laprasdrum.com/swift-testing/diving-into-confirmation
It's my first challenge! As a side project, I created a website last month to publish English articles and wrote several articles so that I could post weekly. Today, I am happy to share my first article with you.
This article is an overview of confirmations, the first half of the contents of Swift Testing, about which I spoke in Japan.
https://laprasdrum.com/swift-testing/introducing-confirmation #swift #testing #swifttesting
You are better off mocking URLSession than using a URLProtocol for mocking HTTP requests in your tests. If you don’t want to just take my word for it, you can read about why in my latest blog post: https://nicksloan.com/posts/mocking-urlsession/ #swift #testing #swifttesting
If folks are looking for using Swift Testing with Vapor, you'll encounter all sort of issues.
Here is something that might help you getting out of troubles:
https://github.com/vapor/vapor/issues/3236#issuecomment-2365300507
It's using Lock from @mattiem ; of course. Who would imagine solving a swift concurrency issue without Matt work on it? 😜
Is #swifttesting not able to understand actor isolation? Here it's complaining that my Regex is not Sendable, but I already isolated it to a global actor.
