القائمة
End-to-end testing with Playwright. Page Object Model, flaky test strategies, CI integration. Triggers: e2e, playwright, browser, end-to-end, integration-test, ui-test.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | e2e |
| description | End-to-end testing with Playwright. Page Object Model, flaky test strategies, CI integration. Triggers: e2e, playwright, browser, end-to-end, integration-test, ui-test. |
| allowed-tools | Read, Bash, Write, Edit, Grep, Glob |
<on_start> agentdb read-start Grep for existing Page Objects (pages/*.ts). Check playwright.config.ts exists. </on_start>
Skill-specific: skills/e2e/reference/e2e-research.mdScope — identify critical user paths only (auth, checkout, core workflows). E2E tests are slow; reject requests to test everything. (gate: list of paths defined, count ≤ what team can maintain)
Check existing Page Objects — grep -r "class.*Page" tests/pages/ or equivalent. Extend existing POM before creating new.
(gate: no duplicate selector sets)
Create/update Page Objects — one file per page/component. Locators use data-testid > role > text > CSS (last resort). Selectors in constructor; actions and assertions as methods.
(gate: no inline selectors in test files)
Write tests — test.describe blocks per feature. beforeEach for setup via POM. Each test asserts one outcome.
(gate: no waitForTimeout in any test)
Async correctness — replace all arbitrary timeouts with condition waits:
waitForResponse(r => r.url().includes('/api/...'))locator(...).waitFor({ state: 'visible' })waitForURL(/pattern/)waitForLoadState('networkidle')
(gate: grep -r "waitForTimeout" tests/ returns nothing)Handle flaky tests — detect with --repeat-each=10. Fix root cause (race condition, animation timing, network timing). If fix deferred: test.fixme(true, 'Flaky - Issue #NNN'). Never silent-skip.
(gate: no test.skip() without issue reference)
Configure Playwright — verify playwright.config.ts has: retries: CI ? 2 : 0, forbidOnly: !!CI, trace: 'on-first-retry', screenshot: 'only-on-failure'. See reference for full config template.
(gate: config file present, CI retries ≥ 2)
CI integration — add/verify GitHub Actions workflow: install with --with-deps, upload playwright-report/ as artifact if: always(). See reference for full YAML.
(gate: artifact upload step present)
Run suite — npx playwright test. All tests pass or are explicitly quarantined with issue refs.
(gate: exit 0, or all failures are test.fixme)
<anti_patterns> E2E tests are slow. Test critical paths, not every feature. waitForTimeout is flaky. Wait for specific conditions. CSS classes change. Use data-testid, role, or text. Flaky tests erode confidence. Fix or quarantine immediately. Selectors scattered = maintenance nightmare. Use Page Objects. </anti_patterns>
<on_complete> agentdb write-end '{"skill":"e2e","tests_written":,"page_objects":[""],"flaky_fixed":,"ci_configured":}'
Record tests added, page objects created, and CI status. </on_complete>
Solution exploration and implementation. Generate 2-3 approaches, pick simplest. Never implement first idea. Triggers: build, implement, create, feature, add.
Systematic debugging methodology based on Zeller's scientific method. Reproduce, hypothesize, predict, test, isolate via binary search, fix root cause. Every fix gets a regression test. Triggers: bug, error, fix, broken, not working, fails, crashed, unexpected, stack trace, regression, exception.
Testing methodology and strategy. Tests prove behavior, not implementation. Triggers: test, tests, coverage, assertion, mock, fixture, spec, verify.
Git workflow and version control best practices. Atomic commits, conventional messages, branch strategies, merge protocols. Triggers: commit, branch, merge, rebase, git, push, pull, PR, version control.
Security best practices and vulnerability prevention. Input validation, authentication, secrets management, OWASP top 10. Triggers: security, auth, authentication, secrets, credentials, vulnerability, injection, XSS, CSRF, rate-limit.
REST API design patterns. Resource naming, status codes, pagination, error responses, versioning. Triggers: api, rest, endpoint, route, http, status-code, pagination.