ui-test is a YAML-first E2E runner built on Playwright.
Record flows, replay them, and improve selector/assertion quality with a review-first pipeline.
Repository checkout:
npm run setupGlobal install:
npm i -g "$(npm pack github:ddv1982/easy-e2e-testing --silent)"
ui-test setup --browsers chromiumOne-off run (no install):
npx -y github:ddv1982/easy-e2e-testing setup --browsers chromiumAll command examples below use global ui-test.
| Command | Purpose |
|---|---|
ui-test setup |
Onboarding and provisioning helper |
ui-test play [test] |
Run one YAML test or all tests |
ui-test record |
Record browser interactions into YAML |
ui-test improve <file> |
Improve selectors, add assertions, remove transient runtime failures, retain non-transient failures as required steps |
ui-test list |
List discovered tests |
ui-test doctor |
Show invocation/version diagnostics |
| Flag | Default |
|---|---|
--headed |
off (headless) |
--timeout <ms> |
10000 |
--delay <ms> |
0 |
--wait-network-idle |
on |
--save-failure-artifacts |
on |
--artifacts-dir <path> |
.ui-test-artifacts |
--browser <name> |
chromium |
--no-start |
off (auto-start enabled) |
testDir=e2e, baseUrl=http://127.0.0.1:5173. Auto-start applies to e2e/example.yaml only.
See ui-test <command> --help or the workflow docs for all flags.
- Browser missing:
npx playwright install chromium - Linux dependencies missing:
npx playwright install-deps chromium - Example app not reachable (example test auto-start): verify
http://127.0.0.1:5173or runui-test play --no-start
Full guide: Troubleshooting
ui-test uses Microsoft Playwright for automation/recording.
See THIRD_PARTY_NOTICES.md.
MIT