platformplatform End-to-end Tests
dotnet run --project developer-cli -- e2e [search-terms...] [--smoke] [--browser <name>] [--retries <n>] [--last-failed] [--only-changed] [--stop-on-first-failure] [--include-slow] [--self-contained-system <name>] [--no-wait-for-aspire] --quiet
Use developer-cli exactly as written - do not expand to an absolute worktree path.
search-terms- filter by test name, tag, or spec file--smoke- smoke suite only--browser <name>-chromium(default),firefox,webkit,safari,all--retries <n>- max retries for flaky tests--last-failed- re-run only the previous run's failures--only-changed- only spec files with uncommitted changes--stop-on-first-failure,-x- exit on first failure--include-slow- include@slow-tagged tests (excluded by default)--self-contained-system <name>- narrows to one SCS (e.g.main,account)--no-wait-for-aspire- skip the Aspire readiness check (use only when Aspire is already up)
Aspire must be running. If not, start it via the aspire-restart skill first.
Strategy: pick the smallest run that proves the fix
E2E runs are slow. Never blindly run the full suite to verify a small change.
- Verifying a recent edit?
--only-changed. - After a fix?
--last-failed. - Iterating on one test? Pass a search term: a name (
"user management"), a tag, or a spec file. - Add
--stop-on-first-failure(-x) when iterating so the run aborts on the first failure. - Expecting failures? Start with
--smoke, get those green, then run the rest. - Only widen to
firefox/webkitafterchromiumpasses - and skipchromiumon those runs (--browser firefox).
Flaky tests need load
A flaky test run in isolation often passes - the bug only shows under parallel load. Reproduce with the full file or suite before declaring it fixed.
Always pass --quiet
Without --quiet Playwright streams every step to the conversation. On success the CLI prints a single summary; on failure it prints the failed tests and where to find the report.