Test suite Health Score

Look beyond test count#

A total test count does not show whether the data is current. It also misses unusual deletion activity and tests concentrated in a small number of files.

The Health Score combines four visible factors:

• Recency: how recently the project synced.
• Momentum: additions compared with deletions.
• Churn: the proportion of deleted tests.
• Breadth: how tests are distributed across files.

Use the score as a prompt#

The score is an entry point, not a universal measure of software quality. A mature project can have low growth and still be maintained well. A migration can temporarily create high churn. A small service may reasonably use fewer test files.

The dashboard keeps each factor visible so teams can see why the total changed and move into the relevant tests, files, and commits.

For example, a score can drop because the project stopped syncing, because deletions spiked during cleanup, or because most tests are concentrated in a small number of files. Those causes lead to different conversations, so the dashboard keeps the underlying history available.

Compare a project with itself#

Health signals are most useful as trends within the same project. They can highlight a stale sync, shrinking suite, concentrated structure, or unusual deletion rate. They do not measure assertion quality, production risk, or functional coverage.

The Health Score reference documents the exact calculation and thresholds.

Use the score alongside test suite history, not instead of it. The score flags where to look; the Git-linked changes explain what happened.