qa-dashboard

Discovery Questions

1. What tool do you use for test reporting today? Console output, JUnit XML, HTML reports, or a dedicated platform? Identify the starting point.
2. Who will look at the dashboard? Developers need failure details and traces. QA leads need trends and flakiness. Leadership needs release confidence and defect rates. Each audience needs a different view.
3. What decisions should the dashboard drive? "Is this build safe to release?" "Which tests need fixing?" "Is quality improving sprint over sprint?" Dashboards without a decision context become shelfware.
4. Where do test results live? GitHub Actions artifacts, S3, a database? The storage location determines which dashboard tool is practical.
5. What CI platform? GitHub Actions, GitLab CI, Jenkins? Each has different artifact and reporting integrations.
6. Check .agents/qa-project-context.md first. Respect existing reporting conventions and infrastructure.

Core Principles