agent-e2e-runner

Generates, maintains, and runs end-to-end tests using Agent Browser with Playwright fallback.

5|15|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill agent-e2e-runner-clfigueiredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-e2e-runner
Source: https://github.com/clfigueiredo/hermes-infra-skills/tree/main/.hermes/skills/curso-hermes/agent-e2e-runner
Command: npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill agent-e2e-runner-clfigueiredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It ensures critical user journeys in web applications keep working by creating, maintaining, and executing E2E tests, while managing flaky tests and capturing debugging artifacts like screenshots, videos, and traces. ## Core Features & Use Cases - Test Journey Creation: Writes E2E tests for critical flows (auth, payments, CRUD) using Agent Browser's semantic selectors, with Playwright as a fallback. - Flaky Test Management: Identifies unstable tests via repeated runs and quarantines them with test.fixme() or test.skip(). - Artifact & CI Integration: Captures screenshots, videos, and traces, generates HTML and JUnit XML reports, and integrates tests into CI/CD pipelines. - Use Case: Before a release, ask the agent to run the full Playwright suite, quarantine any flaky tests, and produce an HTML report with failure traces for the team to review. ## Quick Start Ask the agent to create and run an end-to-end test for your login flow using Agent Browser, capturing a screenshot at each key step.

Frequently Asked Questions about agent-e2e-runner

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

FAQPage Schema
How do I write end-to-end tests with Playwright?▼

Write Playwright tests using the Page Object Model pattern with data-testid locators, assertions at key steps, and condition-based waits instead of fixed timeouts. Run them with npx playwright test and view results via npx playwright show-report.

What is the difference between Agent Browser and Playwright for E2E testing?▼

Agent Browser is preferred for its semantic selectors, AI-optimized element references, and built-in auto-waiting, and it runs on top of Playwright. Playwright is used directly as a fallback when Agent Browser is not available.

How do I handle flaky Playwright tests?▼

Identify flaky tests by running npx playwright test --repeat-each=10, then quarantine them with test.fixme() or test.skip() referencing a tracking issue. Common causes include race conditions, network timing, and animation timing.

Why should I avoid waitForTimeout in Playwright tests?▼

Fixed timeouts create race conditions and slow, unreliable tests. Instead wait for conditions such as waitForResponse, element visibility, or networkidle, and rely on the auto-waiting built into locator-based actions.

Can Playwright E2E tests run in CI/CD pipelines?▼

Yes, tests run headlessly in CI with trace set to on-first-retry for debugging failures. Artifacts such as screenshots, videos, traces, and JUnit XML reports are uploaded for pipeline visibility.