agentleFS
Sign inStart free
memi-designmemi-design/design-skills/skills/swift-testing/SKILL.md

swift-testing

Skill7 starsChanged 4 months agoMITView on GitHub

Build an Apple-platform test strategy with Swift Testing for unit and integration coverage, XCTest for UI automation, deterministic fixtures, and concise agent-readable results.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Swift Testing for new Swift unit and integration tests when the project toolchain supports it.

    line 11
  2. Distinctive:

    Keep XCTest and XCUIAutomation for UI tests and existing Objective-C or mixed-language coverage.

    line 12
  3. Distinctive:

    Add parameterized cases for meaningful input matrices instead of copy-pasted tests.

    line 14
  4. Distinctive:

    Test async failure, cancellation, and actor behavior without arbitrary sleeps.

    line 15
  5. Distinctive:

    Run the smallest suite during iteration and the repository test plan before handoff.

    line 16
  6. Distinctive:

    Read references/commands.md for command and result requirements.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swift Testing

Workflow

  1. Identify the behavior contract and the cheapest test layer that proves it.
  2. Use Swift Testing for new Swift unit and integration tests when the project toolchain supports it.
  3. Keep XCTest and XCUIAutomation for UI tests and existing Objective-C or mixed-language coverage.
  4. Isolate time, randomness, persistence, networking, notifications, and device state behind deterministic inputs.
  5. Add parameterized cases for meaningful input matrices instead of copy-pasted tests.
  6. Test async failure, cancellation, and actor behavior without arbitrary sleeps.
  7. Run the smallest suite during iteration and the repository test plan before handoff.

Test pyramid

  • Many fast unit tests for pure behavior and state transitions.
  • Fewer integration tests for persistence, networking boundaries, intents, and dependency wiring.
  • A small set of stable UI tests for critical user journeys and accessibility identifiers.
  • Performance baselines only for paths where regressions matter.

Read references/commands.md for command and result requirements.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free