e2e-testing

Generate Playwright E2E test suites with Page Object Model patterns.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill e2e-testing-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/.agents/skills/e2e-testing
Command: npx skills add https://github.com/luongldptit/move-ticket --skill e2e-testing-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common pain points of building flaky, hard-to-maintain end-to-end test suites for web applications, reducing test breakage from minor UI changes and cutting down on manual test maintenance work.

Core Features & Use Cases

  • Page Object Model (POM) Implementation: Provides reusable, maintainable test page classes to centralize UI element locators and actions.
  • Flaky Test Mitigation: Includes patterns for identifying, quarantining, and fixing race conditions, network timing issues, and animation-related test failures.
  • CI/CD Integration: Offers ready-to-use GitHub Actions workflow configurations for automated test execution in continuous delivery pipelines.
  • Specialized Testing Support: Includes patterns for Web3 wallet connection testing and financial transaction flow validation for critical applications.
  • Use Case: A SaaS engineering team can use this Skill to quickly scaffold a full Playwright test suite for their product, with built-in artifact collection (screenshots, traces, videos) and HTML reporting for failed tests.

Quick Start

Use the e2e-testing skill to generate a complete Playwright test suite with Page Object Model patterns for your web application's core user flows, including CI/CD configuration and flaky test mitigation strategies.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I fix flaky Playwright tests caused by race conditions and network timing issues?

Playwright E2E test suites use the Page Object Model architecture to centralize UI element locators and actions. This structure isolates changes to reusable classes, preventing widespread test breakage from minor UI updates and cutting maintenance work.

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

Playwright test execution integrates into CI/CD pipelines using ready-to-use GitHub Actions workflow configurations. This automates test runs during continuous delivery, capturing screenshots, traces, and videos as artifacts for failed test reporting.

Can I use Playwright for Web3 wallet connection testing and financial transaction flows?

Playwright supports specialized testing patterns for Web3 wallet connection testing and financial transaction flow validation. These patterns allow QA engineers to automate and verify critical transaction flows in web applications reliably.

What is the best way to structure a maintainable Playwright test suite for web applications?

A maintainable Playwright test suite is best structured using the Page Object Model architecture. This approach centralizes UI element locators and actions into reusable page classes, significantly reducing test breakage from minor UI changes.