e2e-testing-expert_skill

This skill designs and validates robust end-to-end test suites using Playwright, POM, visual regression, and Axe-core accessibility for fast, reliable CI.

Python

7

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yuniorglez/gemini-elite-core --skill e2e-testing-expert

SKILL.md5.2 KB

Overview

This skill is a Senior End-to-End (E2E) Test Architect agent focused on Playwright orchestration, visual regression, and high-performance CI/CD sharding. It codifies resilient, auto-waiting test suite patterns using Page Object Model (POM), automated Axe-core accessibility audits, and deep-trace forensic debugging. It is designed to help teams build stable, fast, and debuggable E2E pipelines for modern web apps.

How this skill works

The skill inspects test surfaces to identify critical user flows and applies a conductor protocol to sync environments, activate required integrations, and run tests with trace-enabled CI. It enforces role-based locators, POM architecture, visual regression with masking, and mandatory accessibility checks using @axe-core/playwright. On failures it captures Playwright traces for forensic analysis and recommends sharding strategies to optimize CI throughput.

When to use it

When you need to replace flaky selector-based tests with role/text-based locators for reliability
When adding visual regression checks and masking dynamic content to prevent false positives
When incorporating accessibility audits into every key user flow
When debugging intermittent CI failures with full Playwright traces
When optimizing large suites via sharding and parallelism to meet tight CI time budgets

Best practices

Prefer getByRole/getByText/getByLabel over CSS/XPath; fix accessibility tree rather than adding test-only attributes
Encapsulate page logic and selectors in POM classes; never litter tests with raw locators
Use web-first assertions (expect().toBeVisible()) and avoid fixed timeouts like waitForTimeout
Mask dynamic regions in visual snapshots and set sensible maxDiffPixels
Configure trace: 'on-first-retry' in CI and fail on unexpected console errors

Example use cases

Scaffold POM classes for an onboarding flow and enforce consistent selectors across tests
Add automated Axe-core audits to checkout and profile flows to catch regressions early
Implement visual regression for marketing landing pages with masks for dates and ads
Configure Playwright sharding in GitHub Actions to run thousands of tests under strict time budgets
Use Playwright traces to triage intermittent failures that screenshots and videos cannot explain

FAQ

Role-based locators align tests with the accessibility tree and produce more resilient selectors; if an element lacks a role, work with design to expose it rather than adding test-only attributes.

How do I prevent visual tests from flaking on dynamic content?

Mask dynamic regions (dates, usernames, ads) in screenshots and set conservative diff tolerances; maintain baselines with a review process for intentional UI changes.