Currently, in the Bitbucket Tests repository dashboard, test status categorization is  OK / Healthy / Flaky

Because the system only flags intermittent test behavior, tests that fail consistently (with 100% failure rate) are miscategorized as "Healthy" instead of requiring attention.
As a result:

Tests that are broken / consistently failing do not appear in the "Needs Attention" overview.
Teams cannot easily distinguish between flaky tests unhealthy / consistently failing tests (high failure rate), and healthy tests.

Suggested Solution

Introduce configurable or standard health status attributes in the Bitbucket Tests dashboard:

• Mark tests with high or 100% failure rates as Unhealthy or Broken, separate from the Flaky label.