e2e-testing

Orchestrate Playwright E2E tests with Page Object Model and CI/CD integration.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/adomot/claude-settings --skill e2e-testing-adomot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/adomot/claude-settings/tree/main/skills/aegis/e2e-testing
Command: npx skills add https://github.com/adomot/claude-settings --skill e2e-testing-adomot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwrightを用いた安定的で高速、保守性の高いE2Eテストを構築する課題を解決します。

Core Features & Use Cases

  • Page Object Model (POM) に基づく再利用性と可読性の向上
  • テスト構造と設定: tests/e2e, fixtures, playwright.config.ts の活用
  • フレーキーテスト戦略とテストの分離・管理
  • アーティファクト管理: スクリーンショット、トレース、ビデオ、レポート
  • CI/CD統合とデータ収集の実践

Quick Start

PlaywrightベースのE2Eテストスイートを初期化して実行してください。

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 using the Page Object Model by organizing page objects under tests/e2e, applying fixtures for data-driven testing, and configuring playwright.config.ts to enhance reusability and readability across your test suite.

What is the best way to handle flaky tests in Playwright?

Handle Playwright flaky tests by implementing dedicated flaky-test strategies, separating unstable test cases, and collecting artifacts like screenshots, traces, and videos to diagnose intermittent failures and improve suite reliability.

How do I integrate Playwright E2E tests into CI/CD pipelines?

Integrate Playwright E2E tests into CI/CD pipelines by applying a modular playwright.config.ts setup, enabling fixture-driven data, and configuring automated artifact collection and reporting for scalable, consistent workflows.

Can I collect screenshots and traces as artifacts in Playwright?

Yes, you can collect screenshots, traces, and videos as artifacts in Playwright by configuring artifact management within your test suite, enabling consistent reporting and debugging for CI/CD integration.

Why does my Playwright E2E test suite require fixture-driven data?

Your Playwright E2E test suite requires fixture-driven data to maintain test isolation, support consistent test structure, and enable scalable data collection across modular configurations and CI/CD workflows.