Skip to main content
Free plan, no cardStart free
Suites, runs and planning 6 min read Updated

Analytics Report: pass rates, usage and feature health across the workspace

The Analytics Report is the workspace's own usage and results report: page views, unique users, session length and interactions for the last hour, day, week or month; the overall pass rate and failed tests; which pages are opened but not used; pass and fail per page; a per-user table with a journey view; feature health with error rates; and a monthly summary. Opened from a recording, it narrows to that recording's run history and step analysis. Everything on it exports as CSV, and it is part of every plan.

About this guide

Written for
Engineering managers · QA leads and test managers · Product owners

What it measures

Pick a window: the last hour, 24 hours, 7 days or 30 days. The top row gives total page views, unique users, average session duration, total interactions, the overall pass rate and the failed tests with their share. Below it: hourly traffic for the last day, the top pages by views, and the interaction types. These are figures about the workspace itself, the pages people open and the tests they run, not analytics of the application you test.

Pages opened versus actually used

The usage history separates a page that was opened from a page that was interacted with. A high "Not Used" count on a page means people arrive and leave without doing anything there, which is the first thing to look at when a feature seems unused. A table of usage rates per page sits under the chart, and a second chart gives the pass and fail percentage per page.

People and features

  • The user-wise report counts users, the active ones in the last seven days, the inactive ones, average visits and average features per user, then lists each user with their test runs, pass rate and last activity. View Journey opens one person's page views, unique pages, time spent and runs.
  • Feature health classifies each feature as healthy, warning or critical from its error rate, charts the distribution and the error rates, and names the features that are down.
  • The monthly report charts traffic and test results by month with a summary per month, and a page-details table with views, unique users and average duration.

One recording

Opened from a recording, the report shows that recording's details, total runs, pass rate and average duration, the distribution of results, the run history with each run's id and status, and a step analysis of the first 30 steps with a link to the rest in the recording itself. Quick actions lead to the recording, to visual regression and to all of its runs.

Export and empty state

Export CSV writes the totals, the pages with their views, unique users and average duration, the usage rates and the per-page pass and fail. A new workspace sees "Start using the platform to see analytics data here" until there is something to count.

Questions people ask about this

Whose activity is counted?
Activity in your own workspace: the pages its members open and the tests they run. It does not measure visitors of the application you test.
How far back does it go?
The windows cover up to the last 30 days; the monthly report shows the trend by month.
Can I take the numbers elsewhere?
Yes. Export CSV writes every table on the page for the window you chose.

Source: /documentation/analytics-and-reporting, updated 2026-11-16. Answers are checked against the shipped product on that date.

Found something out of date? The people who build the module answer the contact form on the home page, and corrections to this guide are dated above. Tell us.

This guide is about regression testing, the job that suites, runs and planning serve. Twenty tools, including ours, are compared by job.

Try it against your own app.

Record one flow and get four kinds of evidence back. Judge the results yourself.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India