test.result.analyzer

Parse ctest, Google Test, and sanitizer reports to generate Markdown test analysis summaries.

Updated Aug 9, 2025
One-click install
npx skills add https://github.com/chrislyons/orpheus-sdk --skill test-result-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test.result.analyzer
Source: https://github.com/chrislyons/orpheus-sdk/tree/main/.claude/skills/project/test-result-analyzer
Command: npx skills add https://github.com/chrislyons/orpheus-sdk --skill test-result-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually sifting through extensive test logs and sanitizer outputs to diagnose failures is a tedious and error-prone process. This skill automates the parsing and summarization of test results, including detailed sanitizer reports and coverage metrics, enabling rapid identification of issues and ensuring high code quality standards.

Core Features & Use Cases

  • Comprehensive Test Parsing: Analyzes output from ctest, Google Test, and various sanitizers (ASan, TSan, UBSan).
  • Actionable Failure Summaries: Provides concise reports detailing failing tests, root causes, exact locations, and suggested fixes.
  • Sanitizer Integration: Clearly extracts and interprets errors from AddressSanitizer, ThreadSanitizer, and UndefinedBehaviorSanitizer.
  • Use Case: After a CI build fails due to a test, use this skill to get an immediate, human-readable report. It will tell you not just which test failed, but why (e.g., a heap-use-after-free detected by ASan), and guide you on how to fix it, saving hours of debugging.

Quick Start

Analyze the attached 'ctest_output.txt' and 'asan_report.txt' files to summarize test failures and sanitizer errors.

Frequently Asked Questions about test.result.analyzer

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

FAQPage Schema
How do I analyze test failures from ctest and Google Test output?

Test result analysis parses ctest and Google Test logs to identify which tests failed, extract error messages, pinpoint failure locations, and suggest fixes. Feed test output files to get a structured report showing test names, failure reasons, and module-level summaries for faster debugging.

Can I extract and interpret sanitizer errors from AddressSanitizer, ThreadSanitizer, and UBSan reports?

Yes. Sanitizer report analysis extracts ASan heap-use-after-free, memory leaks, TSan race conditions, and UBSan undefined behavior violations. It produces human-readable summaries with error type, affected code location, and recommended fixes for each sanitizer finding.

What's the best way to summarize test coverage and failures across multiple CI pipeline runs?

Parse test logs and coverage metrics into a structured Markdown report showing per-module results, coverage trends, total pass/fail counts, and sanitizer details. This enables rapid identification of quality issues and regressions across the entire build without manual log inspection.

Do I need to manually parse sanitizer output or can this be automated?

Sanitizer parsing is fully automated. Feed raw AddressSanitizer, ThreadSanitizer, and UBSan reports directly; the analyzer extracts error details, categorizes by type and module, and generates actionable summaries without manual interpretation.

What information does a test analysis report include?

Reports contain test totals and pass/fail counts, per-module failure details with root causes, exact code locations, sanitizer error breakdowns, coverage metrics by module, and recommended fixes—all in structured Markdown for easy review and action.

Can this work with CI pipelines running multiple test frameworks simultaneously?

Yes. The analyzer handles ctest, Google Test, and sanitizer outputs in read-only log analysis mode, making it compatible with CI pipelines that mix multiple test frameworks and produce varied log formats in a single build.