A testing guide for iOS apps written in Swift, including unit tests, interface tests, snapshot tests, mocks, asynchronous code, and dependency injection. Dependency injection means supplying a component's dependencies from outside so it can be tested in isolation.

Use it when adding unit, UI, or snapshot tests, testing async code and actors, creating protocol-based mocks, or designing testable app modules.

It helps developers test app behaviour without relying on real network or storage services, making failures easier to locate and architecture easier to maintain.

ios-testing — Skill for Claude Code and Codex by pproenca

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add pproenca/dot-skills --skill ios-testing

Clone the repo

git clone --depth 1 https://github.com/pproenca/dot-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pproenca/dot-skills/ios-testing/github.svg)](https://agentmods.dev/skills/pproenca/dot-skills/ios-testing)

Your own site

<a href="https://agentmods.dev/skills/pproenca/dot-skills/ios-testing"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/ios-testing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pproenca/dot-skills/ios-testing"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/ios-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,862 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00079	$0.01862
Opus 5	$0.00039	$0.00931
Sonnet 5	$0.00016	$0.00372
Haiku 4.5	$0.00008	$0.00186

Measured 6d ago against content hash ac8d456bd09f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ios-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/.experimental/ios-testing/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

iOS Testing Best Practices

Comprehensive testing guide for iOS and Swift applications, written at principal engineer level. Contains 44 rules across 8 categories, prioritized by impact to guide test architecture decisions, test authoring patterns, and CI infrastructure.

Clinic Architecture Contract (iOS 26 / Swift 6.2)

All guidance in this skill assumes the clinic modular MVVM-C architecture:

Feature modules import Domain + DesignSystem only (never Data, never sibling features)
App target is the convergence point and owns DependencyContainer, concrete coordinators, and Route Shell wiring
Domain stays pure Swift and defines models plus repository, *Coordinating, ErrorRouting, and AppError contracts
Data owns SwiftData/network/sync/retry/background I/O and implements Domain protocols
Read/write flow defaults to stale-while-revalidate reads and optimistic queued writes
ViewModels call repository protocols directly (no default use-case/interactor layer)

When to Apply

Reference these guidelines when:

Writing new unit tests or UI tests for iOS apps
Designing testable architecture with dependency injection
Testing async/await, actors, and Combine publishers
Setting up snapshot testing or visual regression suites
Configuring CI pipelines, test plans, and parallel execution

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Test Architecture & Testability	CRITICAL	`arch-`
2	Unit Testing Fundamentals	CRITICAL	`unit-`
3	Test Doubles & Isolation	HIGH	`mock-`
4	Async & Concurrency Testing	HIGH	`async-`
5	SwiftUI Testing	MEDIUM-HIGH	`swiftui-`
6	UI & Acceptance Testing	MEDIUM	`ui-`
7	Snapshot & Visual Testing	MEDIUM	`snap-`
8	Test Reliability & CI	LOW-MEDIUM	`ci-`

Quick Reference

1. Test Architecture & Testability (CRITICAL)

arch-protocol-dependencies - Depend on protocols, not concrete types
arch-constructor-injection - Use constructor injection over service locators
arch-test-target-separation - Separate unit and UI test targets
arch-testable-import - Use @testable import sparingly
arch-single-responsibility-tests - One assertion concept per test
arch-arrange-act-assert - Structure tests as Arrange-Act-Assert

Read the full file on GitHub · 128 lines

Files

What ships with it

47 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 128 lines · 79 tokens per session scan A ac8d456bd09f

Subscribe to this mod's changes

ios-testing is a skill published in the GitHub repository pproenca/dot-skills (205 stars, last pushed 24d ago), licensed MIT. It adds 79 tokens to every session and 1,862 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

E2E testing Testing Unit testing

axiom-testing

Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.

CharlesWiltgen/Axiom · 38 tokens

designing-tests

Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.

CloudAI-X/claude-workflow-v2 · 48 tokens

test-automation

Execute Vitest and Playwright test suites with result collection and failure analysis.

a5c-ai/babysitter · 0 tokens

testing-blocks

Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.

adobe/skills · 61 tokens

prd-auto-test-loop

A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.

yunshu0909/yunshu_skillshub · 79 tokens

test-automation-expert

Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…

curiositech/some_claude_skills · 133 tokens