swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
Best use case
swift-protocol-di-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
Teams using swift-protocol-di-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/swift-protocol-di-testing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How swift-protocol-di-testing Compares
| Feature / Agent | swift-protocol-di-testing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Swift Protocol-Based Dependency Injection for Testing
Patterns for making Swift code testable by abstracting external dependencies (file system, network, iCloud) behind small, focused protocols. Enables deterministic tests without I/O.
## When to Activate
- Writing Swift code that accesses file system, network, or external APIs
- Need to test error handling paths without triggering real failures
- Building modules that work across environments (app, test, SwiftUI preview)
- Designing testable architecture with Swift concurrency (actors, Sendable)
- Abstracting iCloud, CoreData, or URLSession behind protocols to keep domain logic framework-free
- Creating mock implementations that simulate specific error conditions for deterministic Swift Testing tests
- Applying hexagonal architecture (ports and adapters) to a Swift module for the first time
## Core Pattern
### 1. Define Small, Focused Protocols
Each protocol handles exactly one external concern.
```swift
// File system access
public protocol FileSystemProviding: Sendable {
func containerURL(for purpose: Purpose) -> URL?
}
// File read/write operations
public protocol FileAccessorProviding: Sendable {
func read(from url: URL) throws -> Data
func write(_ data: Data, to url: URL) throws
func fileExists(at url: URL) -> Bool
}
// Bookmark storage (e.g., for sandboxed apps)
public protocol BookmarkStorageProviding: Sendable {
func saveBookmark(_ data: Data, for key: String) throws
func loadBookmark(for key: String) throws -> Data?
}
```
### 2. Create Default (Production) Implementations
```swift
public struct DefaultFileSystemProvider: FileSystemProviding {
public init() {}
public func containerURL(for purpose: Purpose) -> URL? {
FileManager.default.url(forUbiquityContainerIdentifier: nil)
}
}
public struct DefaultFileAccessor: FileAccessorProviding {
public init() {}
public func read(from url: URL) throws -> Data {
try Data(contentsOf: url)
}
public func write(_ data: Data, to url: URL) throws {
try data.write(to: url, options: .atomic)
}
public func fileExists(at url: URL) -> Bool {
FileManager.default.fileExists(atPath: url.path)
}
}
```
### 3. Create Mock Implementations for Testing
```swift
public final class MockFileAccessor: FileAccessorProviding, @unchecked Sendable {
public var files: [URL: Data] = [:]
public var readError: Error?
public var writeError: Error?
public init() {}
public func read(from url: URL) throws -> Data {
if let error = readError { throw error }
guard let data = files[url] else {
throw CocoaError(.fileReadNoSuchFile)
}
return data
}
public func write(_ data: Data, to url: URL) throws {
if let error = writeError { throw error }
files[url] = data
}
public func fileExists(at url: URL) -> Bool {
files[url] != nil
}
}
```
### 4. Inject Dependencies with Default Parameters
Production code uses defaults; tests inject mocks.
```swift
public actor SyncManager {
private let fileSystem: FileSystemProviding
private let fileAccessor: FileAccessorProviding
public init(
fileSystem: FileSystemProviding = DefaultFileSystemProvider(),
fileAccessor: FileAccessorProviding = DefaultFileAccessor()
) {
self.fileSystem = fileSystem
self.fileAccessor = fileAccessor
}
public func sync() async throws {
guard let containerURL = fileSystem.containerURL(for: .sync) else {
throw SyncError.containerNotAvailable
}
let data = try fileAccessor.read(
from: containerURL.appendingPathComponent("data.json")
)
// Process data...
}
}
```
### 5. Write Tests with Swift Testing
```swift
import Testing
@Test("Sync manager handles missing container")
func testMissingContainer() async {
let mockFileSystem = MockFileSystemProvider(containerURL: nil)
let manager = SyncManager(fileSystem: mockFileSystem)
await #expect(throws: SyncError.containerNotAvailable) {
try await manager.sync()
}
}
@Test("Sync manager reads data correctly")
func testReadData() async throws {
let mockFileAccessor = MockFileAccessor()
mockFileAccessor.files[testURL] = testData
let manager = SyncManager(fileAccessor: mockFileAccessor)
let result = try await manager.loadData()
#expect(result == expectedData)
}
@Test("Sync manager handles read errors gracefully")
func testReadError() async {
let mockFileAccessor = MockFileAccessor()
mockFileAccessor.readError = CocoaError(.fileReadCorruptFile)
let manager = SyncManager(fileAccessor: mockFileAccessor)
await #expect(throws: SyncError.self) {
try await manager.sync()
}
}
```
## Best Practices
- **Single Responsibility**: Each protocol should handle one concern — don't create "god protocols" with many methods
- **Sendable conformance**: Required when protocols are used across actor boundaries
- **Default parameters**: Let production code use real implementations by default; only tests need to specify mocks
- **Error simulation**: Design mocks with configurable error properties for testing failure paths
- **Only mock boundaries**: Mock external dependencies (file system, network, APIs), not internal types
## Anti-Patterns to Avoid
- Creating a single large protocol that covers all external access
- Mocking internal types that have no external dependencies
- Using `#if DEBUG` conditionals instead of proper dependency injection
- Forgetting `Sendable` conformance when used with actors
- Over-engineering: if a type has no external dependencies, it doesn't need a protocol
## When to Use
- Any Swift code that touches file system, network, or external APIs
- Testing error handling paths that are hard to trigger in real environments
- Building modules that need to work in app, test, and SwiftUI preview contexts
- Apps using Swift concurrency (actors, structured concurrency) that need testable architecture
## This IS Hexagonal Architecture
The patterns in this skill are hexagonal (ports & adapters) and DDD — just in Swift idioms:
| Swift Pattern | Hexagonal / DDD Concept |
|---|---|
| Small, focused `protocol` (e.g., `FileAccessorProviding`) | Output Port — defines what the domain needs |
| `DefaultFileAccessor` (real implementation) | Outbound Adapter — production implementation |
| `MockFileAccessor` (test implementation) | Test Adapter — injected in tests |
| `actor SyncManager` (injects protocols) | Use Case / Application Service — orchestrates domain + ports |
| Domain `struct` with `let` properties | Value Object — immutable, no framework imports |
| Domain function `throws` domain errors | Domain behavior enforcing invariants |
### Full Hexagonal Example — Domain + Use Case + Adapters
```swift
// MARK: — Domain (no imports from UIKit, Foundation networking, SwiftData)
struct Market: Identifiable, Sendable {
let id: UUID
let name: String
let slug: String
let status: MarketStatus
}
enum MarketStatus: String, Sendable { case draft, active }
enum MarketError: Error {
case invalidName, alreadyPublished(String)
}
func createMarket(name: String, slug: String) throws -> Market {
guard !name.trimmingCharacters(in: .whitespaces).isEmpty else {
throw MarketError.invalidName
}
return Market(id: UUID(), name: name, slug: slug, status: .draft)
}
func publishMarket(_ market: Market) throws -> Market {
guard market.status == .draft else { throw MarketError.alreadyPublished(market.slug) }
return Market(id: market.id, name: market.name, slug: market.slug, status: .active)
}
// MARK: — Output Port (defined in domain)
protocol MarketRepository: Sendable {
func save(_ market: Market) async throws -> Market
func findBySlug(_ slug: String) async throws -> Market?
}
// MARK: — Use Case (depends only on port interface)
actor CreateMarketUseCase {
private let repository: any MarketRepository
init(repository: any MarketRepository) { // inject output port
self.repository = repository
}
func execute(name: String, slug: String) async throws -> Market {
let market = try createMarket(name: name, slug: slug) // domain logic
return try await repository.save(market) // via port
}
}
// MARK: — Outbound Adapter (production implementation)
actor CoreDataMarketRepository: MarketRepository {
// ... CoreData implementation, satisfies MarketRepository implicitly
}
// MARK: — Test Adapter (injected in tests)
final class MockMarketRepository: MarketRepository, @unchecked Sendable {
var saved: [Market] = []
func save(_ market: Market) async throws -> Market {
saved.append(market)
return market
}
func findBySlug(_ slug: String) async throws -> Market? { nil }
}
// MARK: — Test
@Test("CreateMarketUseCase saves a valid market")
func testCreateMarket() async throws {
let repo = MockMarketRepository()
let useCase = CreateMarketUseCase(repository: repo)
let market = try await useCase.execute(name: "Test", slug: "test")
#expect(market.name == "Test")
#expect(repo.saved.count == 1)
}
@Test("CreateMarketUseCase rejects blank name")
func testBlankName() async {
let useCase = CreateMarketUseCase(repository: MockMarketRepository())
await #expect(throws: MarketError.self) {
try await useCase.execute(name: "", slug: "slug")
}
}
```Related Skills
visual-testing
Visual Regression Testing: tool comparison (Chromatic/Percy/Playwright screenshots/BackstopJS), pixel-diff vs AI-based comparison, baseline management, flakiness strategies (masks, tolerances, waitForLoadState), CI integration with GitHub Actions, and Storybook integration.
typescript-testing
TypeScript testing patterns: Vitest for unit/integration, Playwright for E2E, MSW for API mocking, Testing Library for React components. Core TDD methodology for TypeScript/JavaScript projects.
swiftui-patterns
SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.
swift-testing
Swift testing patterns: Swift Testing framework (Swift 6+), XCTest for UI tests, async/await test cases, actor testing, Combine testing, and XCUITest for UI automation. TDD for Swift/SwiftUI.
swift-patterns
Core Swift patterns — value vs reference types, protocols, generics, optionals, Result, error handling, Codable, and module organization. Foundation for all Swift development.
swift-patterns-advanced
Advanced Swift patterns — property wrappers, result builders, Combine basics, opaque & existential types, macro system, advanced generics, and performance optimization. Extends swift-patterns.
swift-concurrency-6-2
Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.
swift-actor-persistence
Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design.
scala-testing
Scala testing with ScalaTest, MUnit, and ScalaCheck: FunSpec/FlatSpec test structure, property-based testing with forAll, mocking with MockitoSugar, Cats Effect testing with munit-cats-effect (runTest/IOSuite), ZIO Test, Testcontainers-Scala for database integration tests, and CI integration with sbt. Use when writing or reviewing Scala tests.
rust-testing
Rust testing patterns — unit tests with mockall, integration tests with sqlx transactions, HTTP handler testing (axum), benchmarks (criterion), property tests (proptest), fuzzing, and CI with cargo-nextest.
rust-testing-advanced
Advanced Rust testing anti-patterns and corrections — cfg(test) placement, expect() over unwrap(), mockall expectation ordering, executor mixing (#[tokio::test] vs block_on), PgPool isolation with
ruby-testing
RSpec testing patterns for Ruby and Rails — factories, mocks, request specs, feature specs, VCR, and SimpleCov coverage.