/gaia-test-mobile-e2e

user-facing

Category:: Testing
Lifecycle phase:: Anytime
Arguments:: [--suite PATH] [--device ID] [--config PATH]

What it does

Executes mobile end-to-end tests via a configured device-farm adapter (Firebase Test Lab, BrowserStack, or Sauce Labs). Dispatches the test suite and returns per-device verdicts plus a composite verdict.

When to use it

You need to run mobile e2e tests against real devices in a cloud lab.

Prerequisites

A device-farm adapter must be configured in project-config.yaml. The Test Execution Bridge must be enabled.

How to invoke

/gaia-test-mobile-e2e
/gaia-test-mobile-e2e --suite ./tests/e2e
/gaia-test-mobile-e2e --device pixel-7
/gaia-test-mobile-e2e --config .gaia/config/project-config.yaml

What it does step by step

See the description above for the high-level flow. The command handles all steps automatically.

Inputs

Input	Source	Description	Example
`--suite`	Argument (optional, default: ./tests/e2e)	Path to the test suite directory.	`/gaia-test-mobile-e2e --suite ./tests/e2e`
`--device`	Argument (optional)	Target a specific device by id (forward-compat).	`/gaia-test-mobile-e2e --device pixel-7`
`--config`	Argument (optional)	Path to project-config.yaml (auto-resolved by default).	`/gaia-test-mobile-e2e --config .gaia/config/project-config.yaml`

Outputs

Per-device verdicts and a composite verdict (PASSED/FAILED/ERROR/TIMEOUT/SKIPPED).

Example session

> /gaia-test-mobile-e2e

Running...
(Command output varies by project and configuration.)

What to run next

Follow the suggestions displayed at the end of the command output.

Troubleshooting

Check that prerequisite files and tools are in place. The command provides specific error messages with guidance when something is missing.