Monitoring · Production issues Preview

Bring what happens after deployment into the same view.

Receive production errors by commit, add reproduction tests to regression coverage, and view pre-release decisions alongside production events. This feature is in preview. Availability and scope are discussed during consultation.

Request a demo Implementation consultation

Receive browser notifications for approval requests, run completion, FAIL decisions, quarantine, low coverage, and case suggestions.

Error intake & regression additions Preview

Production errors become regression tests.

Receive production errors grouped by deployed commit. Recurring errors generate suggested tests that reproduce the screen and inputs. Once approved, they join the regression suite from the next run.

Receive errors grouped by deployed commit and screen
Automatically suggest reproduction test drafts for recurring errors
Approved tests join the regression suite and inform the next release decision
Retain occurrence counts and first-seen times with run records

Error eventTypeError · Order confirmation11 occurrences since deployment → 1 reproduction test draftApproveReject

Scenario	Priority	Automation	Source	Language
Order confirmation · Reproduce TypeError with an out-of-stock item Awaiting approval	Critical	Automation candidate	Production	KO
Payment amount validation — zero, negative, limit	Critical	Automated	Document	KO EN JA
Order list pagination	Medium	Automated	Document	KO EN JA

Approval adds it to the next pre-release regression suiteLinked to commit 1c8e77a

Real user paths & priorities Preview

Real user paths
set the test order.

Prioritize testing using the paths people actually take. If an untested screen appears in a frequently used path, move it up the test plan. Track it using the same screen coverage criteria.

Reflect real usage rankings by screen path in the test plan
Highlight frequently used screens that tests have never opened
Owners review and adjust priorities in the test plan
Review alongside the screen coverage inventory

More about coverage

Before & after deployment Preview

Your pre-release decision,
Connect what happens after deployment.

Place the evaluated run, deployment time, and subsequent errors on one timeline. If errors rise after a PASS release, trace which tests missed that path. Related issues and owner notifications stay connected.

One commit-based timeline: run decision → deployment → error events
Compare post-deployment error increases with the decision point
Link directly from errors to related issues and owner notifications
See the next successful reproduction test run on the same timeline

Commit 1c8e77a · v2.3.1 deployedPreview

Pre-release decision · #49

PASS

Cases47 / 48
Unopened screens2 screens
Security0 critical

14:02
TypeError · Order confirmation11 occurrences since deployment
Add regression test
14:09
Payment API response: 4.1sp95 threshold exceeded
Notify owner
14:20
Unopened screen · My accountTop 3 user paths
Test first

Notifications

Six notifications available today.

Receive browser notifications when decisions need your attention or a verdict is ready.

Approval requested Available now

Notify the QA lead when a run triggered by automation rules awaits approval. The run starts once approved.

Run complete Available now

Receive the decision and passed, failed, quarantined, and skipped counts when a run finishes. Open the report directly.

Decision: FAIL Available now

Get an immediate notification with the cause when critical or major test failures or security findings result in FAIL.

Test quarantined Available now

When a test is quarantined based on inconsistent same-commit results in the last 20 runs, receive its name, browser engine, and flip rate.

Low coverage Available now

When requirements coverage falls below the 80% target and triggers CONDITIONAL, receive the count of uncovered requirements.

Case suggestions Available now

Receive new, updated, and removal suggestions based on PR changes so you can approve or reject them.

Frequently asked questions

Monitoring FAQs

What is included in the preview?

Production error intake, reproduction tests added to regression suites, usage-based priorities, and a timeline connecting pre-release decisions with production events. Timing and project-specific scope are discussed during consultation.

Do we need to replace our observability tools?

No. The goal is to receive their error events and connect them to testing and decisions. Observability integrations are in preview. Tell us your tools and we will review connection options during consultation.

Which notifications are available now?

Six browser notifications: approval requests, run completion, FAIL decisions, quarantine, low coverage, and case suggestions. Email, chat, and webhook notifications are in preview.

What production data is collected?

Error types, occurrence times, affected screens, deployed commit information, and screen-level usage paths. We agree on data scope per project. See Deployment & data handlingfor data handling details.

Who reviews reproduction tests?

An owner must approve generated drafts before they enter the regression suite. With managed QA, experts review drafts, maintain the suite, retest fixes, and write the release memo.

Do production errors change the pre-release decision?

No. The pre-release decision stays as a record of that run. Reproduction tests join regression coverage and inform the next run's decision. Both points remain visible on the timeline.

Talk to us about QA that continues into production.

Start with release decisions and browser notifications. Define the scope of the monitoring preview with us during consultation.