Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →platformplatform/e2e
Run end-to-end Playwright tests via the developer CLI.
Passed 13 of 17 test cases with the skill, and 5 of 17 without it.
and 10 more in the full report
11 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I made some uncommitted edits across a few spec files locally. Please run the end-to-end tests against just my changed files to make sure I didn't break anything.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the command dotnet run --project developer-cli -- e2e | Missed | Passed |
| Includes the flag --only-changed | Missed | Passed |
| Includes the flag --quiet | Missed | Passed |
The instructions your model reads when the skill loads.
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.
E2E runs are slow. Never blindly run the full suite to verify a small change.
--only-changed.--last-failed."user management"), a tag, or a spec file.--stop-on-first-failure (-x) when iterating so the run aborts on the first failure.--smoke, get those green, then run the rest.firefox / webkit after chromium passes - and skip chromium on those runs (--browser firefox).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.
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.
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.