playwright-webapp-testing
Skill0 starsChanged 23 days agoMITView on GitHub
Test authorized local or staging web apps with Playwright, browser logs, screenshots and reproducible frontend regressions.
In this repository28 other files it gives its agents.
- agent-skill-security-auditorSkill
- backend-api-engineerSkill
- backend-debuggingSkill
- backup-disaster-recoverySkill
- code-review-prSkill
- database-transaction-integritySkill
- dependency-supply-chain-auditorSkill
- devops-ci-cdSkill
- documentation-handoverSkill
- frontend-design-directionSkill
- llm-api-integrationSkill
- load-resilience-testingSkill
- mcp-integration-builderSkill
- observability-monitoringSkill
- performance-accessibilitySkill
- privacy-data-governanceSkill
- product-business-analystSkill
- project-bootstrap-environmentsSkill
- qa-release-gatekeeperSkill
- qa-test-strategySkill
- react-artifacts-builderSkill
- security-authorization-auditorSkill
- skill-authoring-toolkitSkill
- skill-evaluation-benchmarkSkill
- software-architectSkill
- technical-project-orchestratorSkill
- theme-design-systemSkill
- visual-assets-designSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Verify server readiness without stopping unrelated active processes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 webapp testing
- Confirm target URL, environment and permissions, test account, run command and non-production fixtures.
- Review current tests and prefer stable accessible locators (roles, names, test IDs) over brittle selectors.
- Verify server readiness without stopping unrelated active processes.
- Exercise risk-based flows including success, loading, empty, errors, validation, permission denial, keyboard use and mobile widths.
- Record console exceptions, failing requests, screenshots and traces where supported; use deterministic fixtures and avoid arbitrary sleeps.
- Reset test data safely; do not perform real payments or destructive actions without permission.
- Report the commit, exact test command, pass/fail/not-run outcomes, expected vs actual and reproduction steps.
Output: executable test plan, evidence, regression candidates and prioritized defects. Do not claim Playwright was run unless it was actually executed.
Demo and evidence
The optional examples/playwright/smoke.spec.ts is an executable template only when a compatible runner and approved local app already exist. The separate examples/frontend-rtl does not auto-run Playwright. Browser observations must be captured from an actual browser run; unit-test passes are not browser-pass evidence.
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.