Test campaign dashboard — aggregated project monitoring

[ThomasMalletCodra]

Description

Provide a dashboard view that aggregates test campaign data across projects and over time. This gives management and QA teams a high-level overview of test health across the organization.

Current behavior

• No aggregated view of test results across projects.
• Each project's test results are isolated.
• No trend tracking or health indicators.

Expected behavior

• A dashboard showing all projects with their latest test status.
• Per-project trend charts: pass rate over time, test count evolution.
• Configurable alerts: "Project X has had failing tests for 3 consecutive runs".
• Summary cards: total tests, pass rate, coverage (if integrated), last run date.
• Drill-down from dashboard → project → campaign → individual test.

Implementation ideas

1. Build on top of the web interface (Lightweight web interface — read-only result viewer #11) and campaign management (Campaign management/Non regression — execution history and release comparison #9).
2. Aggregate campaign data across projects into a central index.
3. Use Chart.js or similar for trend visualization.
4. Store cross-project data in a shared SQLite database or flat JSON files.
5. Periodic data collection from project .moduletester/ directories.

Dependencies

• Requires Campaign management/Non regression — execution history and release comparison #9 (Campaign management) for historical data.
• Requires Lightweight web interface — read-only result viewer #11 (Web interface) for the serving infrastructure.

Acceptance criteria

• Dashboard shows all registered projects and their latest test status
• Pass rate trends are displayed as charts
• Drill-down navigation: dashboard → project → campaign → test
• Dashboard updates automatically when new campaigns are recorded
• Works with multiple independent projects