test-orchestrator

Automate Vitest test discovery, execution, and failure diagnosis in EquipQR projects.

1|Updated Jun 10, 2025
One-click install
npx skills add https://github.com/Columbia-Cloudworks-LLC/EquipQR --skill test-orchestrator-columbia-cloudworks-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-orchestrator
Source: https://github.com/Columbia-Cloudworks-LLC/EquipQR/tree/main/.cursor/skills/test-orchestrator
Command: npx skills add https://github.com/Columbia-Cloudworks-LLC/EquipQR --skill test-orchestrator-columbia-cloudworks-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the discovery of related tests, runs unit and integration tests, captures failures in a structured format, and guides autonomous retry loops to fix issues faster in the EquipQR Vitest suite.

Core Features & Use Cases

  • Run Unit Tests: Runs tests related to modified source files using the project's Vitest-based runner, focusing on changed areas.
  • Run Integration Tests: Executes journey/integration tests to validate end-to-end flows.
  • Debug Spec: Diagnoses and autonomously iterates fixes for a failing spec by reading failures and re-running targeted tests.

Quick Start

Tell it to run related tests for a changed file or to debug a failing spec.

Frequently Asked Questions about test-orchestrator

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

FAQPage Schema
How do I automate running Vitest tests for modified source files?

To automate Vitest tests for modified files, the orchestrator discovers related unit and integration tests, executes the project's runner, and parses failures to guide autonomous fixes.

How does automated failure diagnosis work for failing Vitest specs?

Automated failure diagnosis works by parsing structured failure outputs and autonomously iterating fixes, re-running targeted tests until the failing spec passes.

Can I run both unit and integration tests when debugging a changed Node.js file?

Yes, you can run both unit and integration tests for changed Node.js files, executing focused test runs for unit specs and journey tests to validate end-to-end flows.

What is the best way to auto-fix failing integration tests in Vitest?

The best way to auto-fix failing Vitest integration tests is to use an orchestrator that collects structured failures and runs autonomous retry loops to resolve issues faster.

Do I need a specific test runner setup to orchestrate focused Vitest runs?

You need the project's existing Vitest-based test runner configured for Node.js, allowing the orchestrator to discover related tests and execute focused runs without changing your setup.