e2e-testing

Design end-to-end test suites with Playwright using Page Object Models and CI sharding.

14|5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/oakoss/agent-skills --skill e2e-testing-oakoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/oakoss/agent-skills/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/oakoss/agent-skills --skill e2e-testing-oakoss

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a robust framework for designing and implementing end-to-end (E2E) testing strategies, ensuring the reliability and quality of web applications through best practices in test architecture and execution.

Core Features & Use Cases

  • Test Architecture Design: Structure test suites effectively using patterns like Page Object Model.
  • CI/CD Integration: Optimize test execution for parallel environments with sharding and reporting.
  • Use Case: When setting up a new E2E testing suite for a complex web application, use this Skill to define the Page Object Model structure, implement authentication strategies, and configure CI sharding for efficient parallel execution.

Quick Start

Use the e2e-testing skill to design a Page Object Model for your application's login flow.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I structure a Playwright E2E testing suite using the Page Object Model?

To structure a Playwright E2E testing suite with the Page Object Model, you define page classes that encapsulate element selectors and interactions. This architecture separates test logic from UI locators, reducing maintenance overhead and improving test organization for complex web applications.

How do I configure CI sharding for parallel Playwright test execution?

CI sharding for parallel Playwright test execution involves splitting the test suite across multiple CI runners to optimize execution time. The testing architecture configures shard distribution and aggregates reporting, ensuring efficient parallel processing without overlapping test states.

Can I mock network requests and replay HAR files in Playwright E2E tests?

Yes, you can mock network requests and replay HAR files in Playwright E2E tests. The architecture supports intercepting network traffic using HAR replay and network mocking techniques to isolate test environments and control API response behaviors.

What is the best way to handle authentication flows in E2E testing?

The best way to handle authentication flows in E2E testing is to implement dedicated authentication strategies that bypass UI login for subsequent tests. This approach saves execution time by saving and restoring authentication state, allowing tests to skip redundant login steps.

How do I perform accessibility auditing with axe-core in an E2E test suite?

Accessibility auditing with axe-core in an E2E test suite integrates automated checks into the Playwright execution flow. This mechanism scans rendered pages for accessibility violations during test runs, ensuring compliance standards are met alongside functional testing.

How do I organize and filter E2E tests using tags and annotations?

Organizing and filtering E2E tests using tags and annotations categorizes specific test scenarios within the suite. This architecture allows selective test execution in CI/CD pipelines by targeting only relevant subsets, optimizing test runs and dev feedback loops.