E2e playwright
Skill soden46/syarif-laravel-ai-skills/skills/e2e-playwright
Laravel E2E testing with official Playwright patterns for locators, auth state, seeds, traces, screenshots, CI, and cross-browser workflows.From its SKILL.md
npx -y skills add soden46/syarif-laravel-ai-skills --skill e2e-playwrightAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.8 KB, as published. Nobody here has run it
E2E Playwright
Use this skill when a Laravel task involves Playwright E2E tests, browser workflow coverage, regression tests, screenshots, traces, auth setup, or converting manual browser findings into durable tests.
Use the official microsoft/playwright repository as the source for current Playwright behavior when APIs, CLI, MCP, browser support, locators, traces, or configuration details matter: https://github.com/microsoft/playwright. Prefer the linked Playwright docs and API reference over remembered APIs.
Workflow
- Detect how the project runs Laravel, assets, queues, database, and browser tests: host, Sail, Docker, package manager, Vite, Playwright config, existing test helpers, and CI commands.
- Reuse project-local Playwright patterns first: auth helpers, seed scripts, storage state, route helpers, page objects, fixtures, test IDs, screenshots, and trace settings.
- Seed deterministic data through Laravel factories, seeders, HTTP setup routes, API helpers, or existing test bootstrap. Avoid fragile production-like data dependencies.
- Write tests with user-facing locators first:
getByRole,getByLabel,getByText,getByPlaceholder, andgetByTestIdonly when semantic locators are not stable enough. - Prefer Playwright web-first assertions such as
toBeVisible,toHaveText,toHaveURL,toHaveValue, andtoHaveScreenshotover fixed sleeps. - Cover the high-value user workflow, not every implementation detail. Include success, validation failure, authorization-dependent UI, empty state, loading or queued state, and destructive confirmation when relevant.
- Capture traces, screenshots, videos, or console/network evidence only when they help debug failures or support handoff.
- Run the smallest meaningful Playwright command locally and report skipped browsers, missing services, or environment blockers explicitly.
Laravel Setup Rules
- Authenticate through existing Laravel test helpers when available. If the project uses storage state, create it from a safe test user and never commit real cookies, tokens, or session files.
- Keep
.env, credentials, tokens, private URLs, raw customer data, and real auth state out of tests, screenshots, traces, and fixtures. - Use Laravel fakes for mail, notifications, queues, files, events, and HTTP integrations when the browser flow does not need the real external system.
- Wait for app-specific readiness: Vite assets loaded, Livewire requests settled, Inertia navigation finished, queued job state visible, fonts ready, and network idle only when it is meaningful.
- Add stable
data-testidattributes only when accessible locators are not reliable and the project accepts test IDs.
Playwright And Agent Browser
Use ui-agent-browser when UI/UX design or implementation is still being explored. Use agent-browser for low-token browser inspection, then convert the accepted workflow into Playwright when it should become a repeatable regression test.
Completion Gate
Do not call Playwright coverage complete unless:
- the tested workflow is tied to real Laravel routes, Livewire actions, Inertia pages, or API contracts;
- deterministic setup and teardown exist or the dependency on local state is explicit;
- locators are resilient and user-facing where possible;
- assertions prove behavior and state, not only that the page loads;
- auth, validation, authorization, loading, empty, and success states are covered when relevant;
- screenshots/traces are enabled or captured where failure diagnosis needs them;
- the exact command run and any skipped checks are reported.
Related Skills
using-laravel-standardsui-agent-browserresponsive-ui-testingtestingrunner-selection
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most e2e browser skills give
Counted across 499 of the 513 authors here whose files we hold, read 2026-09-06
- Capture screenshots, videos, and traces on failurein 32 of 499, across 23 files
- Close the browser when donein 22 of 499
- Interact with elements using snapshot refsin 21 of 499, across 20 files
- Wait for specific network responses instead of fixed timeoutsin 20 of 499, across 10 files
- Keep tests independent with no shared statein 19 of 499, across 17 files
- Use Page Object Model classes to encapsulate page interactionsin 19 of 499, across 9 files
- Locate elements with data-testid attributesin 19 of 499, across 10 files
- Quarantine flaky tests with fixme or skipin 17 of 499, across 7 files
- Upload test artifacts after every CI runin 17 of 499, across 8 files
- Wait on conditions instead of using fixed sleepsin 17 of 499, across 13 files
- Clean up test data after each testin 17 of 499, across 16 files
- Test user-visible behavior, not implementation detailsin 16 of 499, across 10 files
Said here and by no other author read
- Detect how the project runs Laravel and browser tests
- Reuse project-local Playwright patterns first
- Seed deterministic data through Laravel factories
- Write tests with user-facing locators first
- Cover the high-value user workflow
- Capture traces, screenshots, videos only when debugging
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.