ag-testar-e2e-batch

Orchestrate Playwright end-to-end test batches with infrastructure validation and automatic retries.

19|4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill ag-testar-e2e-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ag-testar-e2e-batch
Source: https://github.com/andregusman-raiz/a-gusman-claude/tree/main/skills/ag-testar-e2e-batch
Command: npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill ag-testar-e2e-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate end-to-end test suites in batches with infrastructure validation and automatic recovery.

Core Features & Use Cases

  • Pre-flight infrastructure validation (dev server, env vars, smoke tests)
  • Batch execution of test specs with automatic retries
  • Auto-fix for common flakiness (selectors, timing, mocks)
  • Progress logging to /tmp/e2e-progress.md and consolidated reports

Quick Start

Invoke this skill with your project path and optional flags like --batch-size, --max-retries, and --base-url to start a batched E2E run.

Frequently Asked Questions about ag-testar-e2e-batch

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

FAQPage Schema
How do I run Playwright E2E test suites in batches with automatic retries?

You can run batched E2E tests by invoking an orchestration tool with your project path and flags like --batch-size, --max-retries, and --base-url to execute specs in batches with automatic recovery and pre-flight infrastructure validation.

What does pre-flight infrastructure validation check before running E2E tests?

Pre-flight infrastructure validation checks your dev servers, environment variables, and dependencies before executing E2E tests. It ensures the test environment is ready by running smoke tests and validating configurations to prevent false failures.

Can I automatically fix flaky E2E tests caused by timing or selector issues?

Yes, automatic recovery can fix common E2E test flakiness by adjusting selectors, timing, and mocks. The orchestration applies these auto-fixes during batch execution to stabilize unreliable tests without manual intervention.

How do I configure batch execution size and retry limits for E2E test runs?

You can configure batch execution and retry limits using command-line arguments like --batch-size and --max-retries. These flags control how many test specs run per batch and how many times failed tests retry automatically.

Where are E2E test execution progress and consolidated reports logged?

E2E test execution progress is logged to /tmp/e2e-progress.md with consolidated reports. This file captures batch execution status, retry attempts, and infrastructure validation results for tracking test run outcomes.

Why do my E2E tests fail intermittently even when the application logic is correct?

Intermittent E2E test failures often stem from infrastructure issues like unavailable dev servers, missing environment variables, or timing flakiness. Pre-flight checks, automatic retries, and auto-fixes for selectors and mocks address these environmental instabilities.