skills.rest
llmh333
llmh333COMMUNITY
Explore all skills by this author →
GitHub

e2e-testing

Generate Playwright E2E test suites with Page Object Model and CI artifact capture.

Updated Sep 13, 2025
Search Tags:#ci/cd#test automation#playwright#e2e testing#artifact management#page object model#test flakiness
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill e2e-testing-llmh333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/e2e-testing
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill e2e-testing-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2E test suites often become slow, flaky, and hard to maintain, causing teams to lose confidence in releases and waste time debugging nondeterministic failures.

Core Features & Use Cases

  • Playwright E2E patterns: Maintainable folder structure for auth, features, and API coverage that scales with growing UI complexity.
  • Page Object Model (POM): Encapsulated page interactions (locators, navigation, and assertions) that reduce duplication and make tests easier to refactor.
  • Stability and flakiness control: Practices for avoiding race conditions, handling network timing correctly, and quarantining known flaky scenarios.
  • Artifact management: Automated capture of screenshots, traces, videos, and HTML/JUnit/JSON reports to speed up diagnosis.
  • CI/CD integration: A workflow pattern that runs Playwright on push/PR and uploads reports as build artifacts for consistent team visibility.

Quick Start

Use the e2e-testing skill to generate a Playwright E2E suite with a Page Object Model, CI-ready configuration, and artifact capture for failures.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I reduce flaky Playwright E2E test results in CI?▼

Reduce flaky Playwright E2E tests by implementing deterministic waiting strategies, configuring CI retry behavior, and quarantining known flaky scenarios to stabilize UI regression coverage.

What is the best way to structure Playwright end-to-end tests for web apps?▼

Structure Playwright E2E tests using a Page Object Model to encapsulate locators and assertions, organizing folders by auth, features, and API coverage to scale UI complexity.

How do I manage Playwright test artifacts like screenshots and traces?▼

Manage Playwright test artifacts by automating capture of screenshots, traces, and videos alongside HTML, JUnit, and JSON reports to speed up failure diagnosis in CI pipelines.

Does the Page Object Model work well for Playwright auth and API testing?▼

The Page Object Model works for Playwright auth and API testing by encapsulating page interactions, navigation, and assertions to reduce duplication and make tests easier to refactor.

Why does my E2E test suite lose confidence in releases due to race conditions?▼

E2E test suites lose release confidence when race conditions cause nondeterministic failures, resolved by handling network timing correctly and using deterministic waiting strategies.

Related Skills

Explore More Software Engineering Skills→
JaiminVadadoriyaJaiminVadadoriya
1

playwright-skill

Guide Playwright automated web testing across E2E, API, component, visual, accessibility, and security tests.

Community
Advanced
onesmartguyonesmartguy
2

gitlab-ci-patterns

Automate GitLab CI/CD pipelines for build, test, and deployment workflows.

Community
Advanced
ProfPowellProfPowell
1

backend-testing

Scaffold unit, integration, and API tests for Node.js backends.

Community
Advanced
williamzujkowskiwilliamzujkowski
17

e2e-testing

Automate end-to-end web app testing with Playwright or Cypress in CI/CD pipelines.

Community
Intermediate