playwright-planning

Plan Playwright E2E tests by classifying page roles and selecting checklists and test techniques.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/devbasex/ai-plugins --skill playwright-planning-devbasex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-planning
Source: https://github.com/devbasex/ai-plugins/tree/main/plugins/playwright-kit/skills/playwright-planning
Command: npx skills add https://github.com/devbasex/ai-plugins --skill playwright-planning-devbasex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing E2E test coverage often relies on ad-hoc experience, leading to inconsistent test plans and missed edge cases. This Skill grounds Playwright E2E test planning in industry-standard theory (HTSM, ISTQB, FEW HICCUPPS) so every test scenario is traceable to a page role, a checklist item, and a named test technique. ## Core Features & Use Cases - Page role classification: Classify a target URL into roles (lp, list, item, edit, form, search, dashboard, auth, cart-checkout, modal-wizard) using accessibility-tree heuristics via scripts/classify_page_role.py. - Role-based checklists: Apply per-role checklists plus a common checklist covering accessibility (WCAG 2.2), Core Web Vitals, OWASP security, and i18n, marking each item applicable or not with a reason. - Test technique selection: Map page role and data type to mandatory techniques (EP, BVA, Decision Table, State Transition, Pairwise) and FEW HICCUPPS oracle axes. - Use Case: Given a checkout page URL, classify it as cart-checkout, walk the checklist (price recalculation, coupon decision table, PCI DSS trace inspection), then hand off to the authoring Skill to implement pytest tests. ## Quick Start Ask the AI to plan E2E tests for a target URL, for example: "Plan E2E tests for https://staging.example.com/checkout using the playwright-planning skill."

Frequently Asked Questions about playwright-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan E2E tests with Playwright?▼

Start by classifying the target page into a role (lp, list, item, edit, form, search, dashboard, auth, cart-checkout, modal-wizard), then apply the role's checklist and select mandatory test techniques like BVA or Decision Tables. The classify_page_role.py script automates role detection from the accessibility tree.

What is page role classification in E2E testing?▼

Page role classification groups pages by user purpose and test concerns rather than URL structure. Each role has identification heuristics based on accessibility tree signals, a dedicated checklist, and required test techniques, so coverage decisions are objective rather than experience-based.

Which test techniques should I use for a checkout page?▼

Checkout pages require Decision Tables for price, coupon, and shipping combinations, BVA for amount boundaries, and State Transition testing for the cart-to-delivered flow. Risk Testing covers IDOR on order URLs and PCI DSS checks that card numbers never appear in traces.

Does this approach work with pytest-playwright?▼

Yes, the methodology targets pytest-playwright with Python. Test plans map directly to pytest test functions using @pytest.mark.page_role markers, and templates per role serve as starting points for implementation in the authoring phase.

What are the limitations of checklist-based E2E test planning?▼

Checklists cover black-box behavior verifiable through the browser, so server-side log inspection and pure unit-level logic are out of scope. Pages combining multiple roles require applying each role's checklist, which increases planning effort.