Run any Skill in Manus with one click

verify-e2e

Stars1

Forks0

UpdatedJuly 25, 2026 at 02:30

Run Playwright E2E browser tests to verify UI flows end-to-end. Use before declaring work complete, after UI flow changes, or when browser behavior must be validated.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Robert01101101

Robert01101101/VLCouch

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	verify-e2e
description	Run Playwright E2E browser tests to verify UI flows end-to-end. Use before declaring work complete, after UI flow changes, or when browser behavior must be validated.

Verify E2E flows

When to use

Before declaring any UI-related task complete
After changes to pages, navigation, play/watch flows
When unit tests pass but user-facing behavior needs confirmation

Steps

Run E2E suite (starts test backend + Vite automatically):
```
.\scripts\test.ps1 -Layer e2e
```
On failure, view the HTML report:
```
npx playwright show-report
```

Fix using data-testid selectors; re-run:

npx playwright test e2e/specs/home.spec.ts

Run full suite before done: .\scripts\test.ps1 -Layer all

Expected flows

Spec	Flow
`home.spec.ts`	Home loads → browse rows visible → search → hero play (TEST_MODE skips VLC)
`show-detail.spec.ts`	Click show poster → detail page → toggle watched → mark season watched
`play.spec.ts`	Click movie card → Play (TEST_MODE skips VLC)
`settings.spec.ts`	Settings page loads → toggles, version (from `VERSION`), rescan button

Self-correction loop

run playwright → read trace/report → fix UI or spec → re-run affected spec → run full e2e layer

Notes

E2E uses isolated ports (backend 8001, frontend 5174) so your dev servers and VLC are not affected
E2E backend uses APP_ENV=test, TEST_MODE=true (no VLC launch), SCAN_ON_STARTUP=true with fixture media
Prefer page.getByTestId(...) over text selectors
For async UI updates (e.g. watched checkbox), use click() + waitForResponse, not check()

More from this repository

same repository

generate-commit-message

Robert01101101/VLCouch

Run the full test suite (ruff + all layers), fix failures, then draft and commit with a human-readable message. Use when the user asks for a commit message, wants help summarizing changes before committing, or before running git commit.

2026-07-261

verify-backend

Robert01101101/VLCouch

Run and fix backend pytest tests after API, scanner, model, or router changes. Use when modifying backend/app/, adding endpoints, or when API tests fail.

2026-07-261

verify-frontend

Robert01101101/VLCouch

Run Vitest component tests after React component or page changes. Use when modifying frontend/src/ components, pages, or api.js mocks.

2026-07-261

release-version

Robert01101101/VLCouch

Bump VERSION, sync E2E version checks, run the full test suite, and commit only if green — then tag and publish VLCouchSetup.exe. ALWAYS use this skill when the user mentions version, release, bump, semver, tag, ship, publish, next version, prepare release, or cutting a release — even vague one-line prompts.

2026-07-251

maintain-agent-docs

Robert01101101/VLCouch

Keep AGENTS.md, selector rules, verify skills, and CONTRIBUTING.md in sync with code. Use after adding or changing data-testid values, API endpoints, env vars, test file locations, project structure, or verification commands.

2026-07-191

add-api-endpoint

Robert01101101/VLCouch

End-to-end recipe for adding a new API endpoint — router, tests, api.js, UI, and verification. Use when implementing a new backend route that the frontend will call.

2026-07-161

name	verify-e2e
description	Run Playwright E2E browser tests to verify UI flows end-to-end. Use before declaring work complete, after UI flow changes, or when browser behavior must be validated.

Verify E2E flows

When to use

Before declaring any UI-related task complete
After changes to pages, navigation, play/watch flows
When unit tests pass but user-facing behavior needs confirmation

Steps

Run E2E suite (starts test backend + Vite automatically):
```
.\scripts\test.ps1 -Layer e2e
```
On failure, view the HTML report:
```
npx playwright show-report
```

Fix using data-testid selectors; re-run:

npx playwright test e2e/specs/home.spec.ts

Run full suite before done: .\scripts\test.ps1 -Layer all

Expected flows

Spec	Flow
`home.spec.ts`	Home loads → browse rows visible → search → hero play (TEST_MODE skips VLC)
`show-detail.spec.ts`	Click show poster → detail page → toggle watched → mark season watched
`play.spec.ts`	Click movie card → Play (TEST_MODE skips VLC)
`settings.spec.ts`	Settings page loads → toggles, version (from `VERSION`), rescan button

Self-correction loop

run playwright → read trace/report → fix UI or spec → re-run affected spec → run full e2e layer

Notes

E2E uses isolated ports (backend 8001, frontend 5174) so your dev servers and VLC are not affected
E2E backend uses APP_ENV=test, TEST_MODE=true (no VLC launch), SCAN_ON_STARTUP=true with fixture media
Prefer page.getByTestId(...) over text selectors
For async UI updates (e.g. watched checkbox), use click() + waitForResponse, not check()