quality

Validate Playwright E2E test quality against requirements and conventions.

94|49|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/josipjelic/orchestrated-project-template --skill quality-josipjelic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/josipjelic/orchestrated-project-template/tree/main/.claude/skills/quality
Command: npx skills add https://github.com/josipjelic/orchestrated-project-template --skill quality-josipjelic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when writing Playwright E2E tests for new or modified features, investigating failing tests, assessing test coverage gaps, designing a test strategy for a feature, setting up test infrastructure, or verifying that implemented behavior matches requirements.

Core Features & Use Cases

  • Ground tests in requirements: Before creating or updating E2E tests, reference relevant requirements (e.g., FR-XXX) in PRD.md and trace critical paths.
  • Follow testing conventions: Apply Playwright E2E conventions (file structure, naming, and page object models) and use fixtures, storage state caching, and test.use overrides to reduce setup time and flakiness.
  • Anti-flakiness and optimization: Implement deterministic data, wait for real conditions, and use CI-friendly patterns like test retries and artifact uploads.
  • Accessibility and tooling: Integrate accessibility checks and network-mocking strategies to ensure reliable, compliant tests.
  • CI & quality culture: Emphasize coverage philosophy, test reviews, and anti-pattern avoidance to improve reliability and maintainability.

Quick Start

Follow the protocol to create a Playwright E2E test strategy for a new feature.

Frequently Asked Questions about quality

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

FAQPage Schema
How do I write Playwright E2E tests that are grounded in product requirements?

Playwright E2E tests are grounded in requirements by referencing relevant identifiers like FR-XXX in PRD.md to trace critical paths and verify that implemented behavior matches feature expectations.

What is the best way to prevent flakiness in Playwright E2E tests?

Preventing flakiness in Playwright tests involves implementing deterministic data, waiting for real conditions, and using CI-friendly patterns like test retries, storageState caching, and test.use overrides to reduce setup instability.

How do I set up Playwright test infrastructure for a new feature?

Setting up Playwright test infrastructure involves applying standard conventions like file structuring, page object models, fixtures, and network-mocking strategies to ensure reliable and maintainable E2E test execution.

Can I integrate accessibility checks into my Playwright E2E test strategy?

Yes, accessibility checks can be integrated directly into your Playwright E2E test strategy to ensure tests remain compliant, reliable, and aligned with broader quality assurance and coverage philosophies.

How do I assess coverage gaps when investigating failing Playwright tests?

Assessing Playwright test coverage gaps involves analyzing failing tests against feature expectations, reviewing anti-patterns, and tracing critical paths back to requirements to identify missing test scenarios.

Does this Playwright testing approach require specific CI optimization patterns?

Yes, the approach emphasizes CI optimization patterns like artifact uploads, test retries, and deterministic data to improve test reliability, maintainability, and overall execution speed in automated pipelines.