fix-tests

Triage failing tests into root-cause groups and apply targeted code fixes.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill fix-tests-glowingkitty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-tests
Source: https://github.com/glowingkitty/OpenMates/tree/main/.agents/skills/fix-tests
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill fix-tests-glowingkitty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the time-consuming guesswork of debugging test failures by organizing failures into root-cause groups and applying targeted fixes until the suite is green.

Core Features & Use Cases

  • Root-cause triage delegation: Delegates initial analysis to the test-failure-triager subagent using the latest failure artifacts.
  • Console-error correctness enforcement: Fixes application-side console.error causes rather than suppressing failures in tests.
  • Tiered, grouped remediation: Applies fixes grouped by root cause (starting from the highest tier) and validates with reruns of only the failed specs.

Quick Start

Use fix-tests to triage the latest daily test run, apply root-cause fixes, and rerun only the failed specs until all failures are resolved.

Frequently Asked Questions about fix-tests

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

FAQPage Schema
How do I triage failing automated tests by root cause in CI?

To triage failing automated tests by root cause, the system delegates analysis of the latest daily test run artifacts to a subagent, grouping intermittent unit and e2e spec failures for targeted remediation.

What is the best way to fix intermittent test failures without suppressing console errors?

The best way to fix intermittent test failures without suppressing console errors is to enforce application-side correctness by addressing the root cause of console.error outputs directly in the source code rather than masking them in the test suite.

How do I rerun only previously failed specs after applying CI debugging fixes?

To rerun only previously failed specs after CI debugging, the workflow executes targeted test reruns via a dedicated test runner script, validating the applied fixes until the entire test suite is green.

Does this test automation workflow apply to continuous integration and developer environments?

Yes, this test automation workflow applies to both continuous integration and developer environments, specifically targeting scenarios where a subset of unit or e2e specs fails intermittently or due to recent code changes.

Why should I group test fixes by root cause during test triage?

Grouping test fixes by root cause during test triage eliminates time-consuming guesswork by organizing failures into tiered groups, allowing you to apply targeted code changes systematically starting from the highest tier.

What limitations exist when debugging test failures with automated triage?

A limitation when debugging test failures with automated triage is that the process requires delegating initial failure analysis to a specific subagent and depends on executing targeted reruns through a predefined test runner script.