Run mode / Standard Adaptive

Expand coverage when the evidence says it is worth it.

Standard Adaptive adds structured exploration across the supported viewport matrix while keeping the Coordinator, worker leases, and spending boundary in control.

Multi-viewport perspective

Compare desktop, tablet-like, and mobile-like behavior where the run policy calls for those conditions.

Decision-based exploration

Workers investigate assigned scope and return evidence so the Coordinator can choose the next useful action.

Shared coverage memory

The workforce records claims and handoffs to reduce duplicate exploration and make gaps visible.

Bounded concurrency

Five logical collaboration slots do not promise five simultaneous Chromium sessions on every deployment tier.

The workflow

From one URL to evidence you can act on.

  1. 01

    Define the target and mission

    Give the Coordinator an authorized origin, a clear goal, and safe test data.

  2. 02

    Assign bounded worker leases

    Specialized workers receive approved tasks such as core-flow, responsive, or interaction coverage.

  3. 03

    Compare and prioritize

    Review evidence-linked findings across the observed viewport conditions and decide what deserves follow-up.

What adaptive means here

Adaptive does not mean random or unlimited. The Coordinator uses worker reports, coverage claims, target state, and run policy to decide which next check is useful. A worker may propose work, but task leases and approval boundaries govern execution.

See how the collaborating QA team works and when a Quick Smoke check is enough.

Why viewport attribution matters

A layout can work on a wide screen and fail at a narrow breakpoint. Standard Adaptive keeps the observed viewport attached to the evidence so teams can distinguish a responsive defect from a general journey failure.

The result is still evidence about the tested conditions, not a guarantee for every device, browser, or assistive technology.

Starter access and launch boundaries

Starter is the launch tier for Quick Smoke, Standard Adaptive, 980 monthly MU, and governed five-worker collaboration. Deep Matrix remains an alpha, staff, or admin capability during the MVP period.

Compare current access on the functional pricing page and understand live MU usage before starting a larger run.

Questions teams ask
Does Standard Adaptive always use five browsers at once?

No. Starter provides up to five logical collaboration slots, while the active worker set and actual browser concurrency remain governed by run policy and available infrastructure.

Can workers invent new tasks?

Workers can propose useful follow-up work, but the Coordinator and scheduler must approve safe task leases before execution.

Is Standard Adaptive available on Free?

No. Free is limited to Quick Smoke in the current launch entitlement model; the page shows Standard Adaptive as a clear upgrade path rather than hiding it.

Turn your next deploy into a proof, not a guess.

Start with one authorized URL. Matrix QA walks the journey and returns the evidence your team needs to decide what ships.