Reporting & dashboards
Dashboards are arranged by each person over the same data. Reports answer the questions asked outside the QA team – coverage, traceability, release readiness, defects, team activity – and can be scheduled, exported and compared across projects.
Project dashboard
A per-user widget board: pass rate trend, test base growth, case freshness and the active milestone burndown.
The dashboard is arranged by each person, not dictated by the tool: drag widgets into the order you care about and hide the ones you do not. A QA lead watching release readiness and an engineer watching their own runs get different boards over the same data.
Trend widgets read from real history – cumulative case and check growth per week, the pass rate of recent completed runs, and how much of the suite has never been executed or has gone stale.
- Drag-to-arrange widgets, per user
- Pass rate trend, test base growth, test case freshness
- Active milestone burndown with a forecast
- Recent runs, automation trends and team activity
Reports & exports
10+ report types – coverage, traceability, release readiness, defects, team activity – with PDF and CSV export.
Reports answer the questions asked outside the QA team. Coverage and traceability show what is tested and what is not. Release readiness turns a milestone into a go or no-go picture. Defects lists what testing actually found, including issues raised from checklist cells. Team activity shows who did what in a period.
The Reports page opens on a landing with ready-made presets, your saved reports and the full catalog. Every report has one command bar: a picker, chips showing the applied scope, history, a shareable link that re-opens the exact same view, and export. Three things are kept apart on purpose: a saved report is a reusable setup, a snapshot is a result frozen as it was, and a digest is a summary emailed on a schedule.
- Coverage, traceability, release readiness, defects, team activity and more
- Presets for the common questions, so the first result is one click away
- Saved reports, reopened in one click and pinned to the project dashboard with their key numbers
- Snapshots, frozen as they were and compared with each other
- A share link that opens the same report, scope and snapshot for a colleague
- Compare 2 to 6 runs side by side; AI Run Retrospective as Markdown or PDF
- PDF and CSV export, and organization-wide reports across every project
Email digests
Pick one of seven digest templates, a schedule and the recipients, and the status update sends itself.
A digest is a short email built from a template, not a full report: a daily or weekly testing digest, milestone progress until the milestone is done, daily or weekly automation results, and a defects overview with the oldest open issues. You choose the template, the schedule and the recipients, preview the exact email before saving, and QAM Hub sends it from then on.
Templates are deliberately fixed, so a digest always says the same thing in the same order and a reader learns to scan it. Each sent digest is kept as a snapshot, so a number quoted in a meeting can be re-read later, and the testing templates let a checklist-driven team receive checklist numbers instead of test-run numbers.
- Seven templates: daily and weekly testing, milestone progress, daily and weekly automation, weekly and daily defects
- Live preview of the email before the schedule is saved
- Recipient lists that do not require an account
- Every delivery kept as a snapshot, so a sent digest can be re-read
- Testing digests scoped to test runs, checklist runs or both
Cross-project health
One table over every project – pass rate, active runs, open defects, automation coverage, next milestone – with rules you set.
For anyone responsible for more than one project, the useful view is comparative: which projects are healthy, which need attention, and which are in trouble. The health panel derives that verdict from real metrics and an organization-wide rule set.
The rules are yours to edit, and they are organization-wide on purpose – a colour has to mean the same thing to everyone reading the table. The legend is generated from the active rules, so the explanation can never drift from what is actually applied.
- Critical, warning and healthy verdicts per project
- Editable, organization-wide threshold rules
- A legend generated from the live rules
- Pass rate, active runs, open issues, coverage, next milestone, last activity
