junit-report-collector

Name: junit-report-collector
Availability: InStock
Author: orekyuu

Collect JUnit XML test reports and summarize pass, fail, and skip results.

Updated Feb 28, 2026

Search Tags:#testing #ci/cd #debugging #test results #junit #xml reports

Ready to run

npx skills add https://github.com/orekyuu/orekyuu-claude-plugins --skill junit-report-collector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: junit-report-collector
Source: https://github.com/orekyuu/orekyuu-claude-plugins/tree/main/plugins/junit-report/skills/junit-report-collector
Command: npx skills add https://github.com/orekyuu/orekyuu-claude-plugins --skill junit-report-collector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers quickly understand the results of their test suites by collecting, summarizing, and displaying JUnit XML reports, making it easier to identify and fix failing tests.

Core Features & Use Cases

Collect Reports: Locates JUnit XML files (TEST-*.xml or within standard report directories) in a specified directory.
Summarize Results: Provides a Markdown summary of passed, failed, and skipped tests, with details on failures.
Filter Failures: Option to display only the failed tests for focused debugging.
View Output: Extracts and displays system-out or system-err from test reports.
Use Case: After running your test suite, use this Skill to get a quick overview of which tests failed and why, without manually sifting through XML files.

Quick Start

Collect and display a summary of JUnit test results from the current directory.

Frequently Asked Questions about junit-report-collector

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

FAQPage Schema

How do I parse JUnit XML test reports to see which tests failed?▼

You can parse JUnit XML test reports by collecting the XML files to summarize passed, failed, and skipped test outcomes. This process extracts failure details and system output, providing a readable Markdown summary for quick debugging.

How do I generate a test report summary from JUnit XML files in a CI/CD pipeline?▼

Generating a test report summary from JUnit XML files involves locating standard report directories and aggregating the results. It produces a Markdown overview of test outcomes, which is ideal for CI/CD pipeline integration and post-test execution analysis.

Can I filter JUnit XML results to display only the failed tests?▼

Yes, you can filter JUnit XML results to display only failed tests. This filtering option extracts specific failure details and error messages, allowing you to focus on debugging without manually sifting through the entire test suite output.

How do I extract system-out and system-err logs from JUnit XML reports?▼

Extracting system-out and system-err logs from JUnit XML reports involves parsing the XML structure to retrieve standard output and error streams. This displays the captured console output directly from the test reports for debugging purposes.

What is the best way to aggregate JUnit XML reports without manually reading XML?▼

The best way to aggregate JUnit XML reports without manually reading XML is to use a tool that locates TEST-*.xml files and summarizes them. This approach aggregates machine-generated XML files into a human-readable Markdown format, highlighting failures.

Does this test result collector require any specific dependencies to parse XML?▼

No specific dependencies are required to parse XML test results, as the collector operates using standalone scripts. It directly locates JUnit XML files in your specified directory and processes them without needing external libraries.