test-runner

Automate VitalArc test execution with xcodebuild on macOS workstations.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/tanujsutaria/VitalArc --skill test-runner-tanujsutaria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-runner
Source: https://github.com/tanujsutaria/VitalArc/tree/main/.claude/skills/test-runner
Command: npx skills add https://github.com/tanujsutaria/VitalArc --skill test-runner-tanujsutaria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

VitalArc test execution is often manual and error-prone at the session end. This skill automates running tests as a mandatory quality gate, ensuring consistency and reliability before commits or deployments.

Core Features & Use Cases

  • Full test run by default to validate the entire VitalArc codebase.
  • Quick mode (--quick) for fast unit tests to speed up feedback.
  • Coverage mode (--coverage) to generate code coverage reports.
  • Affected mode (--affected) to test only changed files, improving iteration speed.
  • Works in workstation contexts (Xcode-enabled macOS) and integrates with the forked Bash agent for deterministic runs.
  • Use Case: Before merging, run the full suite; after changes, run only affected tests to confirm no regressions.

Quick Start

Run the test runner to execute all tests using the default Full mode. Examples:

  • /test-runner
  • /test-runner --quick
  • /test-runner --coverage
  • /test-runner --affected
  • /test-runner --filter=MyTestPattern

Frequently Asked Questions about test-runner

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

FAQPage Schema
How do I automate iOS test execution as a mandatory quality gate during PR checks?

Automate iOS test execution by running a Bash-based quality gate that invokes xcodebuild across full, quick, coverage, and affected modes. It enforces mandatory testing during workstation builds, PR checks, and feature releases, returning a non-zero exit code on failure to block merges.

What is the best way to run only affected iOS tests after changing files to speed up feedback?

Run affected iOS tests by passing the --affected option to execute only tests covering changed files. This targeted test mode improves iteration speed during development while still enforcing the quality gate before commits or deployments.

Can I generate code coverage reports for my Xcode project using an automated bash workflow?

Generate code coverage reports by executing the test runner with the --coverage option. It drives xcodebuild invocations within an Xcode-enabled macOS workstation environment to produce coverage data alongside standard test execution results.

Do I need an Xcode-enabled macOS workstation to run these automated test workflows?

Yes, an Xcode-enabled macOS workstation with Bash support is required. The automated test runner leverages the forked Bash agent to drive xcodebuild invocations deterministically, ensuring consistent test execution across workstation builds and pull request checks.

How do I filter specific iOS test cases when running an automated quality gate check?

Filter specific test cases by using the --filter=MyTestPattern option when executing the test runner. This passes the pattern directly to xcodebuild, allowing you to isolate and run targeted test suites during your workstation build or PR validation process.

Why does my automated test gate fail with a non-zero exit code during feature releases?

The automated test gate fails with a non-zero exit code when xcodebuild test invocations encounter failing tests. This strict failure mechanism enforces mandatory quality standards, preventing code from passing the gate during workstation builds or feature releases until regressions are fixed.