testing-workflow

Analyze Jest, pytest, and RSpec JSON test reports for failures and pass rates.

Updated Dec 4, 2025

Search Tags:#debugging #qa #analyze #ci #tests #test-results

Ready to run

npx skills add https://github.com/christianearle01/claude-config-template --skill testing-workflow-christianearle01

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-workflow
Source: https://github.com/christianearle01/claude-config-template/tree/main/.claude/skills/testing-workflow
Command: npx skills add https://github.com/christianearle01/claude-config-template --skill testing-workflow-christianearle01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes test result data to surface failures, health metrics, and performance insights, eliminating manual log sifting.

Core Features & Use Cases

Automated result parsing: Reads test result files (JSON, XML, logs) and identifies status (passed/failed/skipped).
Health & performance metrics: Computes pass rate, total duration, and highlights slow tests.
Module-focused views: Filters results by module/suite for targeted debugging.
Guided next steps: Recommends test commands and actions (e.g., re-run failed tests) for CI and local development.
Optional cheat sheet access: Quick-reference commands and patterns for common scenarios.

Quick Start

Start by ensuring your test results exist as test-results.json in your project root, then ask the skill for insights like "What tests failed?" or "Show me test stats."

Frequently Asked Questions about testing-workflow

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

FAQPage Schema

How do I analyze test results from Jest, pytest, or RSpec to find failures?▼

To analyze test results, you can parse standard JSON reports to surface failures, pass rates, and performance insights. This eliminates manual log sifting by reading test result files and identifying passed, failed, or skipped statuses.

How do I get test health metrics and pass rates from JSON reports?▼

Getting test health metrics from JSON reports involves computing pass rates, total test duration, and highlighting slow tests. This provides a concise summary of test health and performance without requiring manual log analysis.

Can I filter pytest or Jest test results by module for targeted debugging?▼

Yes, you can filter test results by module or suite for targeted debugging. This module-focused view reads standard test result formats and computes summaries to help isolate failures within specific parts of your project.

What is the best way to identify slow tests in CI workflows?▼

The best way to identify slow tests in CI workflows is by analyzing test result data to highlight performance insights. It computes total duration and flags slow tests, returning concise guidance and commands for next steps.

Do I need a specific file format to parse test results and get debugging guidance?▼

You need test results saved as a standard format like JSON, XML, or logs in your project root. The analysis reads these files to compute summaries and return recommended test commands and actions for CI and local development.

Why does parsing test logs manually fail to provide actionable CI insights?▼

Parsing test logs manually fails to provide actionable CI insights because it lacks automated health metric computation. Automated parsing computes pass rates and identifies slow tests, returning concise guidance and commands for immediate next steps.