playwright
Write, run, and maintain reliable end-to-end tests with Playwright. Use for test generation, CI integration, trace debugging, and cross-browser validation.
What this skill does
# Playwright Test Engineering
## Current Versions (Verify Before Use)
```bash
npx playwright --version
```
Check [Playwright releases](https://github.com/microsoft/playwright/releases) for the latest version.
## Core Principles
1. **Tests should be deterministic.** No random data, no time-based assertions, no shared state.
2. **Prefer user-visible selectors.** Use `getByRole`, `getByText`, `getByLabel` over CSS selectors.
3. **One assertion per test.** Test one thing. If it fails, you know exactly what broke.
4. **Traces are for debugging, not primary detection.** A failing test should explain itself; traces help when it doesn't.
5. **Parallel by default.** Use fully-parallel mode. Tests must be isolated.
## Test Writing Checklist
- [ ] Uses semantic locators (`getByRole`, `getByLabel`, `getByText`)
- [ ] Avoids `waitForTimeout` — uses explicit waits (`waitForSelector`, `waitForResponse`)
- [ ] Each test has `test.describe` grouping
- [ ] Test data is isolated (no shared accounts, no hardcoded IDs)
- [ ] API calls are mocked or use test-specific data
- [ ] Screenshots/traces are captured on failure
## Codegen Workflow
```bash
# Generate test from user interactions
npx playwright codegen http://localhost:3000
# Run with UI mode for debugging
npx playwright test --ui
# Run with trace viewer
npx playwright test --trace on
npx playwright show-trace test-results/trace.zip
```
## CI Integration
```yaml
# .github/workflows/playwright.yml
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 22
- run: npm ci
- run: npx playwright install --with-deps
- run: npx playwright test
- uses: actions/upload-artifact@v4
if: failure()
with:
name: playwright-report
path: playwright-report/
```
## Common Anti-Patterns
| Anti-Pattern | Why It's Wrong | Fix |
|---|---|---|
| `page.click('.btn-primary')` | Brittle, no semantic meaning | `page.getByRole('button', { name: 'Submit' }).click()` |
| `page.waitForTimeout(1000)` | Flaky, slow | `page.waitForResponse('**/api/data')` |
| Shared test account | State leaks between tests | Isolate data per test |
| No retries in CI | Network flakes cause failures | `retries: 2` in CI |
| Screenshots on every run | Wastes storage | `screenshot: 'only-on-failure'` |
| Hardcoded URLs | Environment-specific breakage | Use `baseURL` config |
| No visual regression | UI changes break layout | Add `expect(page).toHaveScreenshot()` |
## Validation Checklist
- [ ] `playwright.config.ts` has `fullyParallel: true`
- [ ] `retries` configured for CI (2 for CI, 0 for local)
- [ ] `projects` cover required browsers (Chromium minimum, +WebKit for Safari)
- [ ] Trace configured: `trace: 'on-first-retry'`
- [ ] `globalSetup` handles test data seeding if needed
- [ ] `testResultsDir` is in `.gitignore`
## Official Resources
- [Playwright docs](https://playwright.dev/)
- [Best practices](https://playwright.dev/docs/best-practices)
- [API reference](https://playwright.dev/docs/api/class-page)
- [Trace viewer](https://playwright.dev/docs/trace-viewer)
- [CI configuration](https://playwright.dev/docs/ci)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.