e2e

Execute End To End tests with the configured runner (Cypress, Playwright, or Maestro — see End-to-end testing). For the web runners the command also starts the dev server for the run and tears it down afterwards.

archibald e2e|e [options]

Run without options for an interactive prompt, or pass them directly.

Options

Option	Description
-e, --environment [name]	Environment to use.
-t, --tenant [name]	Tenant to use.
-p, --platform [name]	Platform to test.
-po, --platformOverride [name]	Override platform to use. Platforms are configured in Archibald config under project/platforms property.
-l, --language [name]	Language to use.
-d, --device [desktop|mobile]	Device/viewport to test.
-m, --mode [development|production]	App-server compile mode, like serve/build: development starts archibald serve; production runs archibald build and serves the output. Defaults to cli.e2e.serverMode.
-b, --browser [name]	Browser: chrome, firefox, webkit (Cypress also electron).
-r, --runner [runner]	E2E runner: cypress (default) or playwright for web, maestro for native (React Native/Expo). Defaults to cli.e2e.framework. See archibald maestro.
--test [path]	Provide a path or glob which tests should be executed.
-h, --headless	Run headless instead of opening the UI.
-q, --quiet	Don't use the interactive cli; run with default options.

Note: --mode previously selected the device (desktop/mobile); that now lives under --device. Passing --mode desktop|mobile still works but logs a deprecation warning and is treated as --device.

Example:

archibald e2e -e local -t netconomy-b2c -p shop -d desktop -m production -b chrome -h