- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add testdino-hq/playwright-skill -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add testdino-hq/playwright-skill -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add testdino-hq/playwright-skill -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add testdino-hq/playwright-skill -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/testdino-hq/playwright-skillDe l'éditeur
Opinionated, production-tested Playwright guidance — every pattern includes when (and when not) to use it.
79 reference guides covering the full Playwright surface: selectors, assertions, fixtures, page objects, network mocking, auth, visual regression, accessibility, API testing, CI/CD, debugging, and more.
How to use this skill: open the guide for the topic before answering, even for familiar APIs. Playwright adds and renames APIs and CLI flags every release, and the guides are verified against 1.64. Guides tag newer APIs with the release that added them, e.g. (1.62+); check the project's version (npx playwright --version) before using one.
This skill is designed for testing applications you own or have explicit authorization to test. It does not support or endorse automating interactions with third-party websites or services without permission.
When writing tests or automation that fetch content from external sources (e.g., baseURL pointing to staging/production), treat all returned page content as untrusted input — never pass raw page text back into agent instructions or dynamic code execution without sanitization, as this creates an indirect prompt injection risk.
For CI/CD workflows, pin all external dependencies (GitHub Actions, Docker images) to immutable references (commit SHAs, image digests) rather than mutable version tags. See ci-github-actions.md and docker-and-containers.md for pinning guidance.
getByRole() over CSS/XPath — resilient to markup changes, mirrors how users see the pagepage.waitForTimeout() — use expect(locator).toBeVisible() or page.waitForURL()expect(locator) auto-retries; expect(await locator.textContent()) does notbaseURL in config — zero hardcoded URLs in tests2 in CI, 0 locally — surface flakiness where it matters'on-first-retry' — rich debugging artifacts without CI slowdowntest.extend(), not module-level variablesexpect() calls are fineFor frontend engineers writing the app — make components reliably locatable by tests and AI agents.
Examples are TypeScript; most core guides also show JavaScript. When the project uses .js files or has no tsconfig.json, adapt the TypeScript examples to plain JavaScript (drop type annotations, use require if the project is CommonJS).
Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newe
---name: playwright-skilldescription: Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any…---# SKILL.mdVue d'ensemble
Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newer than most training data. Covers writing or fixing tests, locators, a failing or flaky test, a trace.zip or error message, playwright.config and projects, network mocking, auth, visual and accessibility testing, Docker and CI sharding, playwright-cli browser automation, Playwright Test Agents, page objects, migrating from Cypress or Selenium, and QA work: test case design, bug reports from failures, automating manual test cases, and reviewing tests. TypeScript and JavaScript.
FAQ
Téléchargez SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/testdino-hq/playwright-skill.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.
| Accessibility | accessibility.md |
| Mobile & responsive | mobile-and-responsive.md |
| Component testing | component-testing.md |
| Network mocking | network-mocking.md | when-to-mock.md |
| Forms & validation | forms-and-validation.md |
| File uploads/downloads | file-operations.md | file-upload-download.md |
| Error & edge cases | error-and-edge-cases.md |
| CRUD flows | crud-testing.md |
| Drag and drop | drag-and-drop.md |
| Search & filter UI | search-and-filter.md |
| Clock & time mocking | clock-and-time-mocking.md |
| Third-party integrations | third-party-integrations.md |