Skip to content
SyntaxisSyntaxisSyntaxis

tests

Sets up testing infrastructure. Testing is opt-in; this is the explicit setup path.

Invocation

Section titled “Invocation”
/tests            stack-native unit testing
/tests unit       the same
/tests browser    a browser and end-to-end harness
/tests mobile     a device or simulator harness

Mode selection

Section titled “Mode selection”

A runner name alone never selects browser or mobile setup. /tests Playwright stays a unit request with a runner preference to clarify — not permission to install browser automation.

Defaults

Section titled “Defaults”
Mode Default choice
unit Vitest, pytest, go test, cargo test, by stack
browser Playwright Test
mobile Flutter integration_test; Maestro for React Native; Appium for cross-platform native

An existing runner is always reused rather than replaced.

What it guarantees

Section titled “What it guarantees”
  • One mode per invocation.
  • Unit setup may add tests to an existing Verify command; browser and mobile setup will not add their slower gates to Verify or CI without a separate request.
  • No mode creates CI just by being invoked.
  • An empty suite is never treated as a pass.
Section titled “Related”

This sets up the harness. /automate writes tests into it. See Testing Setup.