Feature Health Dashboard

The feature health dashboard gives you a bird’s-eye view of your entire test suite. See which tests are passing, failing, or flaky at a glance, triage bugs, and get automatic notifications when test health changes.

Dashboard Overview

The dashboard shows your test suite health across all collections:

Status	Meaning
Passing	Test consistently passes across recent runs
Failing	Test is consistently failing

Health is calculated from your recent test run history, so it reflects the current state of your suite — not just the latest run. You can also identify flaky tests — tests that alternate between passing and failing — by reviewing their recent run history in the dashboard.

---

Bug Management

When tests fail, Checksum creates bug entries that you can triage and track.

Triage Workflow

Status	Meaning
Needs Triage	New failure — hasn’t been reviewed yet
Confirmed	Reviewed and confirmed as a real issue
Fixed	Bug has been resolved in code
Not Bug	Marked as a false positive
Snoozed	Acknowledged but deprioritized for now (can be applied from any status)

Bug Details

Each bug includes:

• The failing test(s)
• Failure history and frequency
• Related commits and PRs
• Screenshots and error messages

You can add comments and attachments to bugs for team collaboration — share context, link to related issues, or attach debugging notes.

---

Notifications and Reports

Get automatic notifications about your test suite health via your team’s communication channels.

Supported Channels

• Slack — via webhook or bot integration
• Microsoft Teams — via webhook
• Discord — via webhook
• Google Chat — via webhook
• Email — enable in Settings -> Notifications tab

Report Segmentation

Segment your health reports by tags to get focused views of specific feature areas. For example, you might want separate reports for “Checkout” tests vs “Admin” tests.

Automatic Delivery

Configure reports to be sent automatically after test runs complete. Your team stays informed without having to check the dashboard manually.

---

Activity History

The dashboard tracks all test health changes over time:

• When a test started failing
• When it was healed
• When bugs were triaged
• Historical pass/fail trends

This helps you understand patterns — which areas of your app cause the most test maintenance, and how effective auto-healing has been.

---

Next Steps

• Set up coding agent integration
• Learn about auto-healing