What problem does it solve? Swift code that directly touches the file system, network, or external APIs is hard to test deterministically, making error paths and edge cases nearly impossible to verify without real I/O. ## Core Features & Use Cases - Focused Protocol Design: Define small, single-responsibility protocols (file system, file access, bookmark storage) with Sendable conformance for actor-safe concurrency. - Mock Implementations: Build configurable mocks with in-memory storage and injectable error properties to simulate failure paths like missing files or read errors. - Swift Testing Integration: Write deterministic tests using Swift Testing's #expect macros to verify both success and error handling behavior. - Use Case: When building a SyncManager actor that reads from an iCloud container, inject a MockFileAccessor that throws CocoaError to verify the sync logic handles read failures gracefully without touching disk. ## Quick Start Refactor my Swift SyncManager to use protocol-based dependency injection and write Swift Testing tests with mocked file system errors.