e2e-testing

Generate Playwright E2E test suites with Page Object Model patterns.

Updated Mar 11, 2026

Search Tags:#ci/cd #test automation #flaky tests #playwright #e2e testing #page object model

Ready to run

npx skills add https://github.com/yzlin/supa-opencode --skill e2e-testing-yzlin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/yzlin/supa-opencode/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/yzlin/supa-opencode --skill e2e-testing-yzlin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and maintenance of robust End-to-End (E2E) tests using Playwright, ensuring application stability and reliability.

Core Features & Use Cases

Page Object Model (POM): Implement maintainable and scalable test architectures.
Test Structure & Configuration: Define clear test suites and configure Playwright for various environments.
Flaky Test Management: Strategies for identifying, quarantining, and fixing unreliable tests.
Artifact Generation: Automatic capture of screenshots, videos, and traces for debugging.
CI/CD Integration: Seamless integration into continuous integration pipelines.
Use Case: Develop a comprehensive E2E test suite for a web application, covering critical user flows like authentication, data submission, and payment processing, ensuring a high-quality user experience.

Quick Start

Use the e2e-testing skill to generate a Playwright test file for the login page.

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?▼

To structure Playwright E2E tests with the Page Object Model, you should separate page interactions into dedicated classes and define clear test suites. This approach ensures your test architecture remains scalable and maintainable across various environments.

What's the best way to manage flaky tests in Playwright?▼

Managing flaky tests in Playwright involves implementing strategies to identify, quarantine, and fix unreliable tests. You can configure automatic artifact capture, including screenshots, videos, and traces, to debug the root causes of test instability.

How do I integrate Playwright test automation into a CI/CD pipeline?▼

Playwright test automation integrates into CI/CD pipelines by configuring the test runner to execute suites during continuous integration. This seamless integration automatically generates debugging artifacts like traces and videos for any failed critical user flows.

Can I use Playwright for web3 wallet and financial flow E2E testing?▼

Yes, Playwright can be used for web3 wallet and financial flow E2E testing. The testing patterns support critical user flows like authentication, data submission, and payment processing, ensuring high-quality reliability for complex web applications.

Why do my Playwright tests fail and how do I capture traces for debugging?▼

Playwright tests may fail due to timing issues or application changes, but you can capture traces for debugging through automatic artifact generation. Configuring artifact management records screenshots, videos, and traces to quickly identify the root cause.