html-report
Capabilities
Emit a single .html embedding:
- ECharts charts via CDN—pies, bars, lines, heatmaps, Sankeys, …
- Structured tables
- Summary KPI cards
- Localized legends, axes, tooltips
Files land in session outputs via write_file; the web UI previews them inside a sandboxed iframe isolating scripts from host pages.
When to use
| Scenario | Suggested viz |
|---|---|
| Code review rollup | Severity pie + file-level bars + drill table |
| Defect analytics | Heatmap (module × phase) + Sankey defect→root cause |
| Review KPIs | Trend lines + comparative bars |
| ASPICE tracing | Matrix + Sankey requirement→test |
| Coverage reporting | Donut + stacked bars + grouped tables |
Authoring workflow
Two steps—step two is mandatory guardrail:
Rendering diagram…
Rich dashboards typo easily—one stray
}whitescreens every chart while the HTML looks fine until you inspect the console.
Invocation
Examples:
- "Pie chart severity distribution"
- "Ship a review KPI board"
- "HTML dashboard with plots"
Output traits
| Trait | Detail |
|---|---|
| Self-contained | One file; CDN-served charts |
| Offline-friendly | CDN failure paths can fall back to vendored snippets |
| Sandboxed UI | Iframe sandbox keeps scripts contained |
| Responsive | Works on desktops & wallboards |
Real deliverables
The ASPICE engineering-loop demo shipped four dashboards from html-report:
A-aspice-traceability-dashboard.htmlB-change-impact-dashboard.htmlC-test-coverage.htmlD-coverage-dashboard.html
See ASPICE engineering loop case (demo deliverables section).
Related docs
- document-editing — Word variant of reports
- xlsx — spreadsheet pivots instead of charts