Igor Tarasenko Saik0s

The Ultimate Swift Testing Playbook (2024 WWDC Edition, expanded with Apple docs from June 2025)

Updated with info from https://developer.apple.com/documentation/testing fetched via Firecrawl on June 7, 2025.

See also my blog: See also my blog post: https://steipete.me/posts/2025/migrating-700-tests-to-swift-testing

A hands-on, comprehensive guide for migrating from XCTest to Swift Testing and mastering the new framework. This playbook integrates the latest patterns and best practices from WWDC 2024 and official Apple documentation to make your tests more powerful, expressive, and maintainable.

1. Migration & Tooling Baseline

You are an AI assistant tasked with creating a highly engaging, personalized check-in flow for a user. This flow should emulate a beautifully designed iOS app, focusing on simplicity, clear call-to-actions, and an overall delightful user experience. Your role combines that of a personality coach and an expert UX designer.

Here's the theme for today's check-in: {{THEME}}

And here's the context we have about the user: <user_context> {{USER_CONTEXT}}

How to

Default meta prompt collection: https://gist.github.com/pyros-projects/c77402249b5b45f0a501998870766ae9

Meta prompt collection with creating summaries and context sync (use them when using Cline or other coding assistants): https://gist.github.com/pyros-projects/f6430df8ac6f1ac37e5cfb6a8302edcf

Create a plan

Domains.plist

Documentation of /System/Library/Backup/Domains.plist. File taken from iOS 16.4 iPhone SE 3. The file was removed in iOS 17.0

Values

Values in the plist. Other than SystemDomains, these are not really important and are just here for preservation sake.

A domain in domains.plist contains keys that determine what gets backed up for what types of devices and where (i.e. iCloud vs iTunes). Not all domains have each key. The only 2 keys that must be in every domain are RootPath and RelativePathsToBackupAndRestore. Some domains have the value ShouldDigest. I am not sure exactly what it means but I have included it for documentation purposes.

Version: "24.0"
SystemDomains: (Dictionary), see below

	@available(iOS 15.0, *)
	public struct RichTextEditor : SwiftUICore.View {
	public init(text: SwiftUICore.Binding<Foundation.AttributedString>)
	@_Concurrency.MainActor @preconcurrency public var body: some SwiftUICore.View {
	get
	}
	@available(iOS 15.0, *)
	public typealias Body = @_opaqueReturnTypeOf("$s7SwiftUI14RichTextEditorV4bodyQrvp", 0) __
	}
	@available(*, unavailable)


	<TEMPLATE>
	<INSTRUCTIONS>
	Use the <CODEBASE> code as reference, and convert the high-level <TASK> into a set of very detailed step-by-step instructions that an AI coding agent can complete.
	Only includes steps an AI coding agent can take. Do not include testing or any other work a human would do to confirm the task has been completed.
	ALWAYS have the agent run a build when it is complete. Be specific and decisive about what the agent should do.
	Do not include any additional meta instructions to the user. Use markdown formatting.
	</INSTRUCTIONS>
	<TASK>

	You are an assistant that engages in extremely thorough, self-questioning reasoning. Your approach mirrors human stream-of-consciousness thinking, characterized by continuous exploration, self-doubt, and iterative analysis.

	## Core Principles

	1. EXPLORATION OVER CONCLUSION
	- Never rush to conclusions
	- Keep exploring until a solution emerges naturally from the evidence
	- If uncertain, continue reasoning indefinitely
	- Question every assumption and inference

	"""Use Whisper and llama3 to transcribe and summarize a podcast.
	"""

	from pathlib import Path

	import modal
	from modal import Image, App, method

	LOCAL_OUT = REMOTE_OUT = "./out/podcast_summarize"
	GPU = modal.gpu.A10G()

	import AVFoundation
	import CoreMedia
	import CoreAudio

	protocol AudioFilePlayerDelegate: AnyObject {
	func didReceiveAudioSample(_ buffer: AVAudioPCMBuffer, time: AVAudioTime)
	}

	class AudioFilePlayer: NSObject {
	private var audioFile: AVAudioFile?