Diagnose macOS test failures across Xcode and SwiftPM with focused reruns.
npx skills add https://github.com/AarnavBaddam/skills --skill test-triage-aarnavbaddam
Please help me install this Agent Skill. Skill: test-triage Source: https://github.com/AarnavBaddam/skills/tree/main/test-triage Command: npx skills add https://github.com/AarnavBaddam/skills --skill test-triage-aarnavbaddam
xcodebuild test for Xcode projects or swift test for SwiftPM packages. - Failure Classification: Distinguishes build failures, assertion failures, crashes, async flakes, environment issues, and entitlement problems. - Focused Reruns: Reruns only the failing case instead of the full suite when no new information would be gained. - Use Case: A SwiftPM package fails in CI. Use this Skill to run the smallest failing target, identify the failure as an async timing flake rather than a regression, and get a concrete next rerun or fix step. ## Quick Start Use the test-triage skill to run the smallest failing test scope in my Swift package and explain why the tests are failing.High-intent search queries and answers about installing and using this skill.
Use swift test with a filter flag, such as swift test --filter TestClassName/testMethodName, to run only the failing case. This avoids full-suite reruns and gives faster, more focused feedback on the specific failure.
Use xcodebuild test with the -only-testing flag to target a specific test target, class, or method. Start with the smallest likely failing target before running the full suite to isolate the failure quickly.
A build failure means the code did not compile, so no tests actually executed. A test failure means compilation succeeded but an assertion, crash, or timeout occurred during execution, and each requires a different fix path.
Intermittent failures are usually async timing issues or flakes rather than real regressions. Mark them as likely flakes, rerun the focused case to confirm, and avoid overstating confidence without repeated evidence.
Yes, some tests assume iOS-only or simulator-only behavior and fail under SwiftPM or macOS hosts. Call out these environment assumptions when classifying failures so they are not mistaken for product bugs.
PallepadehatBootstrap, build, and package macOS apps with SwiftPM without Xcode.
Negentropy-LabyAnalyze CI logs and test histories to identify intermittent failures.
Teng-bioDiagnose CI pipeline failures and distinguish deterministic failures from flaky tests.
CharlesWiltgenRuns XCUITests with xcodebuild and parses results using xcresulttool.