test-reporting-dashboards

name	Test Reporting & Dashboards
description	Building test reporting dashboards with real-time execution metrics, trend analysis, flaky test detection, coverage visualization, and integration with Allure, ReportPortal, and custom dashboards using Grafana and Prometheus.
version	1.0.0
author	thetestingacademy
license	MIT
tags	["test-reporting","dashboards","allure","reportportal","grafana","prometheus","metrics","analytics","visualization","trend-analysis"]
testingTypes	["unit","integration","e2e","api","performance"]
frameworks	["playwright","vitest","jest","cypress"]
languages	["typescript","javascript","python"]
domains	["web","backend","devops"]
agents	["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp"]

Test Reporting & Dashboards Skill

You are an expert in building test reporting systems and quality dashboards. When the user asks you to set up test reporting, create quality metric dashboards, integrate with Allure or ReportPortal, or build custom reporting pipelines, follow these detailed instructions.

Core Principles

1. Actionable metrics over vanity numbers -- Report metrics that drive decisions: defect escape rate, flaky test trends, time-to-fix, and coverage gaps rather than just pass/fail counts.
2. Real-time visibility -- Teams need to see test results immediately after execution. Build streaming or near-real-time reporting, not batch overnight reports.
3. Trend analysis over point-in-time snapshots -- A single test run is noise. Track trends over weeks and months to identify systemic quality improvements or degradations.
4. Flaky test identification -- Automatically detect and report tests that inconsistently pass or fail. Flaky tests erode confidence in the entire suite.
5. Multi-dimensional filtering -- Allow users to slice reports by test type, feature area, browser, environment, and time range for targeted investigation.
6. Automated alerting -- Configure alerts for quality threshold breaches: coverage drops, new flaky tests, unusual failure spikes, and execution time increases.
7. Integration with development workflow -- Reports should integrate into PR reviews, Slack channels, and CI/CD dashboards where developers already work.

Project Structure

test-reporting/
  collectors/
    vitest-collector.ts
    playwright-collector.ts
    jest-collector.ts
    generic-junit-collector.ts
  processors/
    result-aggregator.ts
    trend-calculator.ts
    flaky-detector.ts
    coverage-analyzer.ts
  storage/
    database-schema.ts
    result-store.ts
    migration.ts
  dashboards/
    quality-overview.ts
    execution-trends.ts
    flaky-tests.ts
    coverage-report.ts
    team-performance.ts
  exporters/
    allure-exporter.ts
    html-exporter.ts
    json-exporter.ts
    slack-notifier.ts
    github-pr-commenter.ts
  config/
    reporting-config.ts
    alert-config.ts
  api/
    report-api.ts
    webhook-handler.ts

Test Result Collector

// collectors/vitest-collector.ts
export interface TestResult {
  id: string;
  name: string;
  : ;
  : ;
  :  |  |  | ;
  : ;
  ?: { : ; :  };
  : ;
  : ;
  : [];
  : ;
  ?: ;
}

   {
  : ;
  : ;
  : ;
  : ;
  : ;
  : ;
  : ;
  : ;
  : [];
  : ;
  : ;
  : ;
}

  ():  {
   : [] = [];

   ( file  jsonReport. || []) {
     ( test  file. || []) {
      results.({
        : ,
        : test.,
        : test..(),
        : file.,
        : test. ===  ?  : test. ===  ?  : ,
        : test. || ,
        : test.?. > 
          ? { : test.[], : test..() }
          : ,
        : ,
        :  ().(),
        : [],
        : process.. || ,
      });
    }
  }

   passed = results.( r. === ).;
   failed = results.( r. === ).;
   skipped = results.( r. === ).;

   {
    : ,
    :  ().(),
    : jsonReport. || ,
    : results.,
    passed,
    failed,
    skipped,
    : results. >  ? (passed / results.) *  : ,
    results,
    : process.. || ,
    : process.. || ,
    : process.. || ,
  };
}