e2e

Generate and execute Playwright end-to-end tests across multiple browsers.

Updated Feb 10, 2026

Search Tags:#automation #testing #ci/cd #web development #e2e #playwright

Ready to run

npx skills add https://github.com/ihj04982/my-cursor-settings --skill e2e-ihj04982

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/ihj04982/my-cursor-settings/tree/main/skills/e2e
Command: npx skills add https://github.com/ihj04982/my-cursor-settings --skill e2e-ihj04982

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the generation and execution of end-to-end tests for web applications, ensuring critical user journeys function correctly and reliably.

Core Features & Use Cases

Automated Test Generation: Creates Playwright tests for user flows using the Page Object Model.
Cross-Browser Execution: Runs tests across Chromium, Firefox, and WebKit.
Artifact Capture: Collects screenshots, videos, and trace files on test failures for debugging.
CI/CD Integration: Provides configurations for seamless integration into CI/CD pipelines.
Use Case: Automatically test the entire user login and checkout process before deploying new code to production.

Quick Start

Use the e2e skill to test the market search and view flow.

Frequently Asked Questions about e2e

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

FAQPage Schema

How do I generate end-to-end tests for web applications using Playwright?▼

You can generate end-to-end tests by creating Playwright test journeys for user flows using the Page Object Model. This automates test creation for critical web application paths, ensuring they function correctly before deployment.

What is the best way to automate cross-browser testing for critical user journeys?▼

Automating cross-browser testing runs your end-to-end tests across Chromium, Firefox, and WebKit. This validates critical user journeys across different browser environments to ensure reliable web application functionality.

Does this approach capture screenshots and videos when an e2e test fails?▼

Yes, the end-to-end testing approach captures screenshots, videos, and trace files upon test failures. These artifacts provide debugging context to help identify why the web application test failed.

Can I integrate automated Playwright tests into my CI/CD pipeline?▼

Yes, you can integrate automated Playwright tests into CI/CD pipelines using provided configurations. This ensures end-to-end tests run automatically during deployment to catch issues in critical user flows.

How do I identify flaky tests in my end-to-end test suite?▼

The end-to-end testing process identifies flaky tests within your suite. By running automated user flows repeatedly across browsers, it detects inconsistent test results that indicate instability in the test logic.

Why use the Page Object Model for automated e2e test generation?▼

The Page Object Model structures generated end-to-end tests by separating user interface elements from test logic. This makes the automated Playwright test journeys easier to maintain and scale as the web application evolves.