Skip to main content

Introduction

TrueCoverage connects real user behaviour with your test efforts so you can see exactly which user pathways are covered by tests and which are not. Unlike typical product analytics tools, TestChimp tracks the same event emits during test runs as in production. That alignment lets you tie test insights directly to the behaviours real users exhibit—and surface coverage gaps in a way that drives prioritization.

What TrueCoverage Unlocks​

TrueCoverage gives you capabilities and insights that sit at the intersection of product behaviour and QA:

  • Drop-offs: See where users leave a flow (e.g. after a specific step or event) and whether you have tests covering that path.
  • Dwell: Identify steps where users spend a long time before moving on—potential friction or confusion—and whether those steps are tested.
  • Friction points: Spot events or transitions that correlate with slow progression or abandonment.
  • Funnel shape: Understand the real user funnel (which events happen in what order, how often) and compare it to what your tests exercise.
  • Discovery issues: See how long it takes users to reach key events (e.g. first use of a feature)—indicators of discoverability—and whether those journeys are covered.
  • Coverage gaps: Answer “users are dropping off here—and there is no test covering that path” or “users are struggling at this step, and here are the usability/performance bugs around that which were uncovered by exploratory agents.”

By aligning production event data with test execution data, TrueCoverage highlights where real user behaviour is not covered by tests, so you can close high-impact gaps first.

How It Differs From Typical Product Analytics​

Typical product analytics software focuses on understanding user behaviour in production only. TestChimp goes further:

  • Same events in test runs: Events are emitted in both production (via testchimp-rum-js) and during test execution. The Playwright TestChimp runner augments event emits with test identification details, so TestChimp can align test runs with the same event taxonomy used in production.
  • Test coverage over real behaviour: You can define a “base” scope (e.g. production or a specific environment) for event funnels and frequencies, and a “coverage” scope (e.g. test runs). TrueCoverage then overlays which events and pathways are covered by tests, so you see coverage relative to what users actually do.
  • Prioritization by frequency: Use relative event frequencies and metadata breakdowns to prioritize testing—e.g. “this event variant is very common in production but has no test coverage.”

Together, this lets you identify high-priority test gaps (e.g. “users are dropping off here—and there is no test covering that path”) and connect exploratory findings (e.g. usability or performance bugs) to the same steps where users struggle.

Prioritizing Testing Efforts​

You can use TrueCoverage to prioritize testing by:

  • Relative frequencies: Focus test design on the most frequent events and transitions.
  • Metadata key values: Drill down into metadata (e.g. form_of_payment, checkout_step) to see which variations of an event are common and which are covered—so you can add tests for high-frequency variants that lack coverage.

These inputs help you address “users are dropping off here” and “there is no test covering that path” in a data-driven way, and to align exploratory agent findings (e.g. bugs at a given step) with real user behaviour.

Next Steps​

  • How it works — Events, sessions, metrics, and event transitions.
  • Dashboard — Overview, event detail, funnel, sample sessions, and metadata slicing.