Skip to content
KaDeep Docsv4.0
Open StudioDownload

Monitoring and reliability

For managers and QA leads2 min readUpdated for v4.0

Your view

Two pages tell you whether testing itself is healthy. Live ops is the now: what runs, what it costs, what errors. Reliability is the trend: which tools fail, which tests are flaky or slow.

In the sidebar, open Workspace › Operations. Live ops is the first tab. Press Ctrl K (Windows) or ⌘ K (Mac), type Live ops, and press Enter.
Live ops: the Right now tiles, the time window and Pause updates (Manage view)
Live ops: the Right now tiles, the time window and Pause updates (Manage view)

Manage view

Live ops: the Right now tiles, the time window and Pause updates (Hands-on view)
Live ops: the Right now tiles, the time window and Pause updates (Hands-on view)

Hands-on view

  • 1 Right now: runs active, agents busy, the queue, devices online, errors in the last hour, cost per hour and today, and monitors.
  • 2 The window for the charts: 15m, 1h, 6h or 24h. Narrow it to one project with Project.
  • 3 The page updates every 5 seconds. Pause updates freezes it while you read.

The charts below show runs started, passed and failed, and tokens and cost, over the window. Show data lists the numbers behind a chart.

Choose the Reliability tab.

Reliability: the summary line, tool error rates by family, and the failure heatmap (Manage view)
Reliability: the summary line, tool error rates by family, and the failure heatmap (Manage view)

Manage view

Reliability: the summary line, tool error rates by family, and the failure heatmap (Hands-on view)
Reliability: the summary line, tool error rates by family, and the failure heatmap (Hands-on view)

Hands-on view

  • 1 The summary: runs in the period, the share of agent steps that failed, checks that found a problem, and flaky tests.
  • 2 Tool error rates by family: browser, phone, API and other tools.
  • 3 Failure heatmap: failed runs per project per day.

Further down:

Section What to do with it
Tools that fail most A high error rate on one tool points to a setup problem, such as a login or a device. Healed counts steps that found their target another way.
Slowest tests Split or speed up the slowest ones, so suites finish sooner.
Flaky tests Tests that pass and fail with no change. File bug to have someone fix the test.