test-macos-app

Runs focused macOS test scopes and classifies failures by category.

4.0k|410|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/robinebers/openusage --skill test-macos-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-macos-app
Source: https://github.com/robinebers/openusage/tree/main/.agents/skills/test-macos-app
Command: npx skills add https://github.com/robinebers/openusage --skill test-macos-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running an entire Xcode or Swift test suite on every change is slow, and raw test output makes it hard to tell whether a failure is a compile error, a real assertion failure, or an environment issue. This Skill runs the smallest meaningful test scope first and explains failures by category so you can act on the top blocker immediately.

Core Features & Use Cases

  • Focused Test Execution: Detects whether the repo uses xcodebuild test or swift test and prefers targeted runs when a scheme, target, or filter is provided.
  • Failure Classification: Categorizes failures as compile, assertion, crash, env/setup, or flake, and separates build failures from actual failing tests.
  • Use Case: After editing a Swift package, invoke the skill with a test filter to rerun only the affected tests, then get a summary of the top blocker and the narrowest sensible next step instead of a wall of logs.

Quick Start

Invoke /test-macos-app with an optional scheme, target, filter, or configuration to run the smallest relevant macOS test scope and get a categorized failure summary.

Frequently Asked Questions about test-macos-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run only specific macOS tests instead of the full suite?

Invoke the skill with a target or filter argument, and it prefers focused test execution over a full suite run. It detects whether the repo uses xcodebuild test or swift test and builds the narrowest command for your selection.

How to tell if a Swift test failure is a compile error or a real assertion failure?

The skill classifies each failure into compile, assertion, crash, env/setup, or flake categories. Build failures are explicitly distinguished from actual failing tests so you fix compilation issues before interpreting test results.

Does this work with both xcodebuild and swift test?

Yes, the workflow first detects whether the repository uses xcodebuild test or swift test and adapts its execution accordingly. It supports optional scheme, target, filter, and Debug or Release configuration arguments.

Why do macOS tests fail due to environment or setup issues?

Failures often come from host app setup requirements or simulator-only test assumptions leaking into a macOS run. The skill flags these as env/setup failures and notes when simulator assumptions are the cause.

When should I rerun the full test suite instead of a focused scope?

The skill avoids rerunning the full suite whenever a focused rerun is possible, since targeted runs are faster and clearer. A full suite run is only sensible when failures span multiple unrelated targets or the focused scope cannot reproduce the issue.