Skip to main content
Insights page: Trends
The Insights page is your project’s health report. It’s under Analytics in every project’s sidebar and answers three questions in one screen: what needs attention right now, how is quality trending, and what happened lately.

​
How to Read This Page

At the top, TestSprite also surfaces contextual prompts when they apply — e.g. “We noticed changes in your repo” with a Re-run all tests button when your code has moved since the last run, or a suggestion to enable the GitHub Action for a connected repo.

​
Issues to Fix (Triage Queue)

The queue lists every test case whose latest result is failed or blocked, but one row is one root cause, not one test. Failures with the same diagnosis (same HTTP status and error signature) are clustered together, so a single backend bug that breaks eight tests shows up as one row tagged “8 tests”, not eight rows. How it’s sorted: failed groups above blocked ones → groups containing a regression first → the largest cluster first (one fix clears the most tests). Blocked tests are collapsed behind a “Blocked · N tests that could not run” toggle so they don’t bury real failures. Badges to look for: Clearing the queue, item by item:
1

Expand the top row

Click a row to see the Suggested fix and the affected tests. Click any test pill to open its detail drawer without leaving the page.
2

Decide: real bug, flaky test, or stale test

A New badge points at a regression; a Flaky badge points at instability. For anything ambiguous, check the test’s historical results in its detail view.
3

Act, then re-run

For product bugs, click Copy Fix Prompt to copy a ready-made prompt (diagnosis, endpoint, response, suggested fix, affected tests) and paste it into your coding agent. After a fix — or for suspected flakes — hit the row’s Re-run button to re-run every affected test at once.
There’s no manual “dismiss” — the queue is fully derived from results. A row disappears the moment its tests pass on a re-run. When the queue is empty you’ll see “Nothing to fix.”
The Trends widget plots one point per run (up to the last 50 runs — not calendar time), across four metrics. Each card shows the current value, a sparkline, and a delta arrow vs. the previous run (green = moving the right way): How to interpret common patterns:
  • Failing several runs in a row — likely a real regression; check what changed around the first failing run (the Activity Log helps here).
  • Alternating pass / fail — a flaky test or unstable environment, not a product bug; these also get the Flaky badge in the triage queue.
  • Sudden drop across many tests at once — usually an environment or authentication problem rather than many simultaneous bugs.

​
Use Case Coverage

Use Case Coverage — category and pass-rate donuts above the All / Covered / Planned / Gap suite table
  • Use Case Coverage breaks your use-case map into Covered / Planned / Gap tabs with per-suite pass rates. Rows flagged Gap have a Generate tests shortcut; Planned rows have Run tests. Low-pass-rate rows are tinted so weak suites stand out.

​
Project Activity Log

The Activity Log — all project activity, newest first, with user and event-type filters
The activity feed lives on its own page: in the project sidebar, open Activity Log (under Activity). It lists all project activity, newest first — each row shows who did what to which entity, and when, with before → after values for edits. Recorded activity covers the full project lifecycle: test cases created/edited/deleted, use cases generated, runs triggered and completed, schedules created or paused, environments and sources changed, members joining or changing roles, GitHub triggers, and Slack/email notifications sent. Filter the feed by user, time window (last 24 hours / 7 days / 30 days / all time), or event type — useful for answering “who changed this test?” or “what happened right before the pass rate dropped?”.

​
Suggested Workflow: Weekly Quality Review

Run your weekly quality meeting directly off this page:
  1. Clear the triage queue — walk Issues to Fix top to bottom; the sorting already puts the highest-leverage fix first.
  2. Read the Trends deltas — a falling pass rate or rising regressions is the week’s headline.
  3. Scan Use Case Coverage — assign any Gap rows before the next release.
  4. Skim the Activity Log — confirm nothing unexpected changed (tests deleted, schedules paused).

​
Where to Go Next

Test Report & Export

Download a shareable PDF report for any run

Rerun

Re-run a single test, a failure group, or the whole project