skills.rest
hjemmesidekongen
hjemmesidekongenCOMMUNITY
Explore all skills by this author →
GitHub

playwright-testing

Enforce Playwright best practices for locators, assertions, and fixtures.

1|Updated Mar 1, 2026
Search Tags:#testing#e2e#qa#browser automation#playwright#ci
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill playwright-testing-hjemmesidekongen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-testing
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/smedjen/skills/playwright-testing
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill playwright-testing-hjemmesidekongen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers write more reliable, maintainable, and efficient end-to-end browser tests using Playwright, by enforcing best practices and identifying common pitfalls.

Core Features & Use Cases

  • Locator Strategy Enforcement: Guides users to employ semantic and accessible locators.
  • Assertion Best Practices: Promotes the use of Playwright's auto-waiting assertions.
  • Fixture Model Guidance: Encourages reusable test setup and state management.
  • CI/CD Integration: Provides advice on parallelization, retries, and reporting for CI environments.
  • Use Case: Ensure all new Playwright tests in a project adhere to the established locator hierarchy and avoid hard waits, leading to more stable test suites.

Quick Start

Review the provided references/process.md document for detailed guidance on Playwright best practices.

Frequently Asked Questions about playwright-testing

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

FAQPage Schema
How do I write robust Playwright browser tests that don't use brittle selectors?▼

Write robust Playwright browser tests by enforcing semantic and accessible locator strategies, which avoids brittle selectors and improves long-term test maintainability across your suite.

What's the best way to handle Playwright auto-waiting assertions instead of hard waits?▼

The best way to handle Playwright assertions is using built-in auto-waiting assertion patterns, eliminating unstable hard waits and ensuring reliable test execution without arbitrary delays.

How do I optimize Playwright test suites for reliable CI execution?▼

Optimize Playwright tests for reliable CI execution by configuring parallelization, retries, and reporting, addressing common anti-patterns to stabilize your end-to-end test runs in pipeline environments.

Can I manage reusable test setup and state in Playwright using fixtures?▼

Yes, you can manage reusable test setup and state in Playwright using the fixture model, which encourages organized state management and reduces duplicated configuration across browser tests.

Why do my Playwright end-to-end tests fail intermittently in CI?▼

Playwright end-to-end tests fail intermittently in CI due to anti-patterns like hard waits and brittle selectors; adopting auto-waiting assertions and semantic locators resolves these timing issues.

Related Skills

Explore More Software Engineering Skills→
browserbasebrowserbase
3.7k

Browser Automation

Automate browser interactions with persistent Playwright sessions via CLI commands.

Official
Advanced
peshaypeshay
1

bmad-testarch-ci

Generate CI/CD pipeline configurations with quality gates and flaky test detection.

Community
Advanced
oimiragieooimiragieo
36

test-generator

Generate unit, integration, API, and E2E tests from specifications and components.

Community
Intermediate
williamzujkowskiwilliamzujkowski
17

e2e-testing

Automate end-to-end web app testing with Playwright or Cypress in CI/CD pipelines.

Community
Intermediate