test-result-analyzer

Analyzes failing test output to identify root causes and prioritize fixes.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/JenilRevaliya/ARGUS --skill test-result-analyzer-jenilrevaliya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-result-analyzer
Source: https://github.com/JenilRevaliya/ARGUS/tree/main/.agent/skills/test-result-analyzer
Command: npx skills add https://github.com/JenilRevaliya/ARGUS --skill test-result-analyzer-jenilrevaliya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a test run produces dozens of failures across many files, developers waste time reading walls of error text without knowing which failure to fix first. This Skill parses test output, clusters related failures, finds the First Point of Failure, and produces a prioritized fix plan. ## Core Features & Use Cases - Runner Auto-Detection: Recognizes output formats from Jest, Vitest, pytest, Go test, Mocha, JUnit, RSpec, and Cargo test. - Failure Clustering & FPF Detection: Groups failures by shared module, error type, fixture, or environment, then identifies the root cause whose fix resolves cascading failures. - Prioritized Fix Plan: Scores each fix by tests resolved, confidence, and estimated time, producing an ordered action plan with verification steps. - Use Case: After a CI run shows 12 failing test files, the Skill detects that 11 failures cascade from a missing export in utils/auth.ts and recommends fixing that single line first to resolve 92% of failures. ## Quick Start Analyze the test output from my last CI run and tell me which failure to fix first.

Frequently Asked Questions about test-result-analyzer

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

FAQPage Schema
How do I find the root cause when many tests fail at once?▼

Find the First Point of Failure by sorting failures in execution order and checking whether the first failing source file appears in other failures' import chains. Fixing that root cause typically resolves the cascading failures automatically.

How to analyze test failures from Jest, pytest, or Go test output?▼

Auto-detect the framework from output patterns: Jest uses PASS/FAIL markers, pytest uses FAILED with :: separators, and Go test uses --- FAIL lines. Then extract each failure's test name, file, error type, and stack trace into structured records.

Which test frameworks does this failure analysis support?▼

It supports Jest, Vitest, pytest, Go test, Mocha, JUnit XML, RSpec, and Cargo test. The framework is auto-detected from output format patterns rather than assumed, so mixed or unfamiliar logs are flagged for manual review.

Why do all my tests fail at the same time?▼

When 100% of tests fail, the cause is usually environmental rather than code. Check whether the database or dev server is running, whether .env.test is missing variables, whether dependencies are installed, and whether a recent dependency upgrade broke compatibility.

Why do tests pass individually but fail when run together?▼

This pattern indicates a race condition or shared mutable state between tests. Check for global state that is not reset in beforeEach hooks, time-dependent assertions, unresolved promises, or network calls without mocks.

When should I update snapshots instead of fixing test failures?▼

If only snapshot tests fail, the UI change is likely intentional. Review the snapshot diffs first; if the changes are expected, rerun with the --updateSnapshot flag, otherwise investigate unintended CSS or component changes.