foryourhealth111-pixel/Vibe-Skills / bundled/skills/generating-test-reports
generating-test-reports
VerifiedGenerate structured test reports with pass/fail rollups, coverage summaries, and test artifacts. Use when the user is asking for test-result packaging or delivery, not for root-cause debugging or feature implementation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| assets/README.md | markdown | 285 B |
| assets/example_config.yaml | config | 2.6 KB |
| assets/report_template.html | other | 3.6 KB |
| assets/sample_test_results.json | config | 3.6 KB |
| references/README.md | markdown | 387 B |
| scripts/README.md | markdown | 592 B |
| scripts/aggregate_results.py | script | 2.9 KB |
| scripts/analyze_trends.py | script | 4.7 KB |
| scripts/generate_report.py | script | 3.7 KB |
assets/example_config.yaml
View on GitHub# Configuration file for the test-report-generator plugin
# --- General Settings ---
report_name: "Automated Test Report" # Name of the report
output_directory: "./reports" # Directory to store generated reports
report_format: "html" # Report output format (html, pdf, json)
timestamp_format: "%Y-%m-%d %H:%M:%S" # Format for timestamps in the report
# --- Data Sources ---
test_results:
type: "junit" # Type of test result files (junit, pytest, etc.)
path: "./test-results/*.xml" # Path to the test result files (supports glob patterns)
# For multiple data sources, define additional entries:
# - type: "pytest"
# path: "./pytest-results/results.xml"
coverage_data:
type: "cobertura" # Type of coverage data (cobertura, lcov)
path: "./coverage.xml" # Path to the coverage data file
# If no coverage data is available, leave this section commented out:
# type: "none"
# path: ""
# --- Report Customization ---
logo_path: "YOUR_LOGO_PATH_HERE" # Path to a logo to include in the report (optional)
report_title: "REPLACE_ME - Project Test Report" # Title displayed in the report
report_description: "Comprehensive test report for REPLACE_ME project, including test results and code coverage." # Description of the report
# --- Thresholds and Alerts ---
pass_rate_threshold: 0.95 # Minimum pass rate (as a fraction) to be considered successful
coverage_threshold: 0.80 # Minimum code coverage (as a fraction) to be considered successful
alert_on_failure: true # Send alerts if any tests fail
alert_recipients: # List of email addresses or channels to send alerts to
- "YOUR_EMAIL_ADDRESS_HERE"
# - "another_recipient@example.com"
# --- Historical Data ---
historical_data:
enabled: false # Enable historical data tracking and comparisons
database_url: "sqlite:///test_report_history.db" # URL for the database storing historical data (e.g., SQLite, PostgreSQL)
retention_period: "30d" # How long to retain historical data (e.g., 30d, 90d, 1y)
# --- Advanced Options ---
include_stacktraces: true # Include stack traces in the report
collapse_long_messages: true # Collapse long test messages for readability
debug_mode: false # Enable debug mode for more verbose logging
# --- Plugin-Specific Options ---
# These options are specific to this test report generator plugin
failure_analysis_enabled: true # Enables automated failure analysis
stakeholder_format: "executive" # Format for stakeholder-friendly report (executive, detailed)Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |