Skip to main content
Documentation
Docs / Products / Coverage
Agent setup

Verify

Coverage

Define roles, devices, data states, and constraints, then compare supplied observations with the resulting state map.

Last updated August 22, 2026

See which product states still need a test.

Use cases

Map the relevant combinations

Describe dimensions and exclude combinations that cannot occur.

Find gaps in observations

See which states have supporting evidence and which remain untested.

Plan the next test

Use the state map to select the conditions your next test should exercise.

How it works

  1. 1

    Define the dimensions

    Describe relevant identities, devices, data, and network conditions.

  2. 2

    Add constraints and evidence

    Exclude impossible states and supply observations from completed tests.

  3. 3

    Review remaining coverage

    Choose the next states to exercise and add the resulting evidence.

Quickstart

Open Coverage in the console, provide the required inputs, and start an organization scoped run.

Inputs

  • deployed URL
  • state model
  • test identities
  • browser policy

Outputs

  • state graph
  • unreachable states
  • transition failures
  • reproduction traces
Open Coverage

MCP

Call Coverage from a compatible agent with the preferred public tool name.

bashReady
symbolic.states.run

The previous internal service identifier remains accepted for compatibility, but new integrations should use this product name.