Skip to navigation
Build and Run Tests

Run Configuration

View as Markdown

Direct Web Runs are available. Review the saved Test and Project target before starting execution. Native Android, iOS, and Desktop execution are not generally available.

Choose the target

Confirm the approved Web Project target before starting a Run. Record the required viewport and location in the saved Test where supported. For Android or iOS, record the app build and device needs. For Desktop, record the application and operating-system needs.

Keep ordering explicit

Tests contain an ordered list of steps. If one journey depends on another, prefer a clear shared setup within its Test Group over an undocumented timing assumption. The CLI and local MCP can dispatch an explicit selection of saved Tests from a Group; each selected Test produces its own Run. Dispatch is not a passing group result, and Tests must not depend on another selected Run having finished. See Run selected Tests from a Group.

Make the result decidable

Every required assertion needs an observable expected outcome. Missing access, setup, or required evidence should produce ERROR, not FAILED.