swift-testing-pro
Skill46 starsChanged 48 days agoMITView on GitHub
Write and review BloomCoreTests using Swift Testing, including async behaviour, isolated fixtures and regression tests.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- lingyired/status-triotheir own version, first seen Nov 8, 2026
- kelvinkosbab/KozBontheir own version, first seen Nov 6, 2026
- molayab/swift-cli-managertheir own version, first seen Nov 1, 2026
- VelimirMueller/claude-skillstheir own version, first seen Nov 1, 2026
- VelimirMueller/ai-development-skillstheir own version, first seen Nov 1, 2026
- Acromegaliacanaliculus452/Swift-Testing-Agent-Skilltheir own version, first seen Oct 25, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- lingyired/status-trio★ 1.8ksame name
- twostraws/Swift-Testing-Agent-Skill★ 423same name
- 199-biotechnologies/swiftui-claude-skills★ 7same name
- VelimirMueller/ai-development-skills★ 7same name
- VelimirMueller/claude-skills★ 7same name
- kelvinkosbab/KozBon★ 5same name
- molayab/swift-cli-manager★ 3same name
- molayab/swift-ai-provider-kit★ 1same name
- Acromegaliacanaliculus452/Swift-Testing-Agent-Skill★ 0same name
- Nelwhix/bloom★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bloom-dev-buildSkill
- bloom-releaseSkill
- swift-concurrency-proSkill
- swiftui-proSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use Swift Testing for new core tests and follow neighbouring suites in Tests/BloomCoreTests.
- Very specific: line 17
Run ./Tools/test-core.sh <filter> for the affected suites.
- Very specific: line 19
Follow CLAUDE.md for required lint and CI checks.
- Very specific: line 22
Keep assertions about observable behaviour.
“Common” is measured: kept by at least 6 in 10 of the 10 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.
Files
Swift Testing in Bloom
Use Swift Testing for new core tests and follow neighbouring suites in Tests/BloomCoreTests.
The target imports BloomCore, not the app. Test presentation decisions in the core; use XCTest
for UI automation if that is requested. Do not migrate unrelated XCTest tests during a review.
Run ./Tools/test-core.sh <filter> for the affected suites. make test runs the whole core suite
but does not compile the app; use make build for app compilation when the change needs it.
Follow CLAUDE.md for required lint and CI checks. Keep real agent calls and machine-dependent
checks opt-in, as documented by Tools/test-core.sh.
Keep assertions about observable behaviour. Lift mutating calls out of #expect: store their
result in a local, then assert on it. Use isolated temporary files, databases and defaults domains.
For reviews, report actual defects with file locations and effects. For test changes, edit the files directly. Check installed toolchain/API availability rather than treating this guide as more authoritative than compiler diagnostics or upstream documentation.
Load only the relevant references:
- Core rules: suites, assertions and parameterised cases.
- Test design: dependencies, errors and useful regressions.
- Async tests: serialisation, completion and cancellation.
- Newer APIs: version-dependent testing features.
- XCTest migration: only for a requested migration.
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
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.