agentleFS
caglarbaranboracaglarbaranbora/Apple-Agent-Kit/skills/testing/SKILL.md

testing

Skill1 starsChanged 3 months agoLicence not identifiedView on GitHub

Route Apple-platform testing tasks to the correct Knowledge Contracts -- XCTestCase subclassing with test-prefixed methods and the per-test setUp()/setUpWithError()/tearDown()/tearDownWithError() lifecycle plus the XCTAssert family and XCTSkip/XCTSkipIf/XCTSkipUnless; the Swift Testing framework's @Test/#expect/#require/@Suite/Tag vocabulary; @Test(arguments:) parameterization (single-collection, two-collection Cartesian product, zip-paired) and async throws test functions in both frameworks; XCUIApplication/XCUIElement UI testing with identifier-based lookup; and XCTestExpectation for callback-based async code with no async/await entry point. Use when writing class Foo: XCTestCase, func test..., override func setUp()/setUpWithError()/tearDown()/tearDownWithError(), XCTAssertEqual/XCTAssertTrue/XCTAssertNil/XCTAssertThrowsError, XCTSkip/XCTSkipIf/XCTSkipUnless, import Testing, @Test, @Suite, #expect(_:), #require(_:), .tags(_:), @Test(arguments:), zip(...) inside @Test(arguments:), async throws test methods, XCUIApplication(), .launch(), continueAfterFailure, app.buttons["..."], .tap(), .typeText(_:), .waitForExistence(timeout:), XCTestExpectation, expectation(description:), .fulfill(), or await fulfillment(of:timeout:). v1 covers only XCTest, Swift Testing, and XCUITest as described -- no performance testing (measure { }, XCTMetric, XCTClockMetric), no Xcode Test Plans or code coverage configuration, no third-party snapshot testing, no UI test recording, no mocking/dependency-injection/test-double patterns, and no performAccessibilityAudit(). Triggers on XCTest, XCTestCase, XCTAssert, XCTSkip, Swift Testing, @Test, #expect, #require, @Suite, Tag, parameterized test, XCUITest, XCUIApplication, XCUIElement, accessibilityIdentifier, XCTestExpectation, fulfillment.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 171 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.

Does it work?

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

Reviews can't be read right now.

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.