e2e-testing

Structure Playwright E2E tests with POM patterns and configuration templates.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/PedroHBO/opencode-config-skills --skill e2e-testing-pedrohbo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/PedroHBO/opencode-config-skills/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/PedroHBO/opencode-config-skills --skill e2e-testing-pedrohbo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Writing and maintaining reliable end-to-end tests for modern web apps can be brittle and time-consuming. This skill provides a structured approach to Playwright-based E2E testing, including Page Object Model (POM) guidance, configuration patterns, and CI/CD integration to reduce flakiness and accelerate delivery.

Core Features & Use Cases

  • Page Object Model (POM) patterns and reusable test structures
  • Playwright configuration templates for multi-browser testing
  • Flaky-test strategies, artifact collection, and reporting templates
  • CI/CD integrations and artifact workflows to improve feedback loops

Quick Start

Run the provided Playwright E2E templates to scaffold tests and adapt the Page Object Model patterns to your app.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I structure Playwright E2E tests using the Page Object Model?

Structure Playwright E2E tests by applying the Page Object Model (POM) pattern to separate test logic from UI locators. This skill provides reusable test structures and POM guidance to reduce flakiness and accelerate test maintenance at scale.

What's the best way to fix flaky Playwright tests in CI/CD pipelines?

Fix flaky Playwright tests by enforcing auto-waiting, robust waits, and data-testid usage. This skill provides flaky-test strategies and standardized reporting templates to stabilize E2E test runs within CI/CD pipelines.

How do I configure Playwright for multi-browser E2E testing?

Configure multi-browser E2E testing using provided Playwright configuration templates. These templates support diverse apps and include CI/CD integration patterns to streamline cross-browser validation and artifact collection.

Does this E2E testing approach work with existing CI/CD workflows?

Yes, this E2E testing approach integrates directly with CI/CD workflows. It provides artifact workflows and standardized reporting templates to improve feedback loops and accelerate delivery across diverse applications.

Why do my Playwright E2E tests fail intermittently during execution?

Playwright E2E tests fail intermittently due to missing auto-waits and non-standardized locators. This skill enforces best practices like data-testid usage and robust waits to eliminate flaky test behaviors and stabilize execution.

Can I scaffold Playwright tests quickly for a new web application?

Yes, you can scaffold Playwright tests quickly using provided templates. The skill supplies E2E test structures and Page Object Model patterns that adapt directly to new web applications for immediate test coverage.