playwright-testing
Playwright E2E testing patterns, cross-browser configuration, page objects, and CI setup. Use when creating E2E specs, visual regression suites, or configuring Playwright in CI. Trigger terms: playwright, e2e, trace, page object, cross-browser
90
96%
Does it follow best practices?
Impact
92%
1.58xAverage score across 2 eval scenarios
Low
Low-risk findings worth noting
Evaluation results
92%
18%Login Flow Testing Without a Live Backend
Deterministic Playwright tests via API mocking
page.route() mocking
100%
100%
Success case mocked
100%
100%
Failure case mocked
100%
100%
Test file placement
100%
100%
test.describe wrapper
100%
100%
Semantic locators — getByRole
0%
100%
No module-level singletons
100%
100%
playwright.config.ts present
100%
100%
fullyParallel enabled
0%
0%
trace on-first-retry
0%
100%
92%
50%TODO List Feature: E2E Test Coverage
Playwright test structure: page objects and semantic locators
Test file location
0%
33%
Page object location
0%
100%
Page object import
80%
100%
Page object instantiation
60%
100%
test.describe usage
100%
100%
getByRole locator
0%
100%
Semantic locator variety
0%
100%
No raw CSS selectors
0%
100%
Add item test
100%
100%
Mark complete test
100%
100%
- Repository
- monkilabs/opencastle
- Commit
7a69a05
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.