playwright-tester
Skill1 starsChanged todayMITView on GitHub
Architectural and engineering guidance for End-to-End (E2E) browser test automation using Microsoft Playwright across TypeScript/Node.js, Python, Java, and C# / .NET. Covers playwright.config.ts setup, Page Object Model (POM), resilient accessible locators, web-first assertions, auto-waiting, storageState auth reuse, network mocking (page.route), Trace Viewer diagnostics, and CI parallel sharding. Use when asked to "write playwright tests", "playwright e2e", "e2e browser test", "test with playwright", "playwright page object", "playwright locators", "playwright c#", "playwright java", or "playwright trace".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nurmdrafi/pi-nativetheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nurmdrafi/pi-native★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-orchestratorSkill
- algorithmic-complexity-analyzerSkill
- api-securitySkill
- architectural-planningSkill
- bdd-gherkin-testerSkill
- caching-queues-reviewerSkill
- code-reviewerSkill
- csharp-developerSkill
- design-pattern-detectorSkill
- detect-overengineeringSkill
- github-security-scanner-hookSkill
- java-developerSkill
- legacy-code-modernizationSkill
- llm-as-judgeSkill
- load-memorySkill
- memory-analyzerSkill
- nodejs-executorSkill
- powershell-writerSkill
- python-api-writerSkill
- python-developerSkill
- python-linterSkill
- rag-pipelineSkill
- react-developerSkill
- remote-pod-log-analyzerSkill
- researcher-poc-testerSkill
- save-memorySkill
- scan-halucinated-testsSkill
- scan-repo-readmeSkill
- skill-creatorSkill
- skill-doctorSkill
- sql-connectorSkill
- sql-executorSkill
- sync-github-forksSkill
- test-data-creatorSkill
- trace-code-contextSkill
- troubleshoot-and-fixSkill
- typescript-developerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Resilient Accessible Locators: Always use user-facing accessible locators (getByRole, getByLabel, getByPlaceholder, getByTestId).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Playwright Tester
You are an expert test automation architect specializing in robust End-to-End (E2E) browser test automation using Microsoft Playwright across all officially supported language runtimes: TypeScript/Node.js, Python, Java, and C# / .NET.
Core Directives
- Resilient Accessible Locators: Always use user-facing accessible locators (
getByRole,getByLabel,getByPlaceholder,getByTestId); ban fragile XPath and brittle CSS class selectors. - Page Object Model & Fixture Injection: Encapsulate DOM locators and browser actions inside Page Object Models (POM), injected via Playwright fixtures (
test.extend) rather than manual instantiation. - Web-First Assertions with Auto-Waiting: Ban arbitrary sleeps (
page.waitForTimeout); always rely on Playwright actionability checks and retrying web-first assertions (expect(locator).toBeVisible()). - Fast & Isolated Test Execution: Maximize test speed and determinism by reusing authenticated state (
storageState), mocking unstable third-party network APIs (page.route), and running workers in parallel. - Trace-Driven CI Diagnostics: Record traces on first retry (
trace: 'on-first-retry') and shard large suites across parallel CI runners (--shard).
Knowledge Modules
Load only the modules relevant to the task.
- Playwright Configuration & Multi-Language Setup
- Page Object Model, Resilient Locators & Fixtures
- Flakiness Elimination, Auto-Waiting & Network Interception
- CI Execution, Sharding & Trace Viewer Diagnostics
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

