Tests Dashboard
The Tests Dashboard is a single GitHub issue, opened by TestQuorum on each repository it watches, that tracks what tests we know about and which ones are failing on your integration branch. It is rebuilt automatically on a schedule so you can keep it pinned and always see the current state.
What's in the issue
When the dashboard is enabled for a repository, TestQuorum opens an issue titled Tests Dashboard and keeps its body up to date. The body answers two questions, in two sections:
Broken Tests
The tests that failed on the latest run on main, along with the short
SHA of that run. If every test passed on the latest run — or no run has
ever been recorded for main — the section is omitted entirely, so a
healthy repository's dashboard does not have an empty Broken Tests
section staring at you.
Tracked Tests
A per-test-manager directory of every test we have ever recorded for the
repository. Each manager (cargo, nix, treefmt, or a custom:<name>
runner you have configured) gets a collapsible block listing the test
names underneath it. Well-known managers are listed first; custom
runners follow alphabetically. Tests recorded without a test manager
set are not shown.
Lifecycle
- The issue is created the first time the reconciler runs for an opted-in repository.
- It is rebuilt on a schedule (currently every 30 minutes), pulling the latest broken-tests and tracked-tests data from the per-repository store on each pass.
- If you close or delete the issue, TestQuorum will open a fresh one on the next reconciliation. To stop the dashboard for a repository, disable it in your repository settings rather than closing the issue.