it-app-e2e-runner

Execute Playwright end-to-end tests and inspect failure artifacts.

Updated May 18, 2026
One-click install
npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill it-app-e2e-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: it-app-e2e-runner
Source: https://github.com/ABLER-Digital-Services/ai-guild/tree/main/skills/it-app-e2e-runner
Command: npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill it-app-e2e-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests frequently fail or slow down delivery when teams run E2E checks inconsistently across local and CI environments; this Skill standardizes how to execute Playwright-based E2E tests and inspect results reliably.

Core Features & Use Cases

  • Playwright E2E execution: Runs full suites, single spec files, or filtered test names using npm scripts and npx Playwright.
  • Debug-friendly workflows: Supports headed mode and interactive UI mode to reproduce and diagnose failures.
  • Result verification & failure analysis: Guides users to check console output and to inspect traces/reports produced in test-results/evidence artifacts.
  • CI alignment: Mirrors GitHub Actions-driven E2E execution and artifact collection so local findings match CI outcomes.

Quick Start

Ask the AI to run E2E tests by executing npm test in the target repository.

Frequently Asked Questions about it-app-e2e-runner

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

FAQPage Schema
How do I run Playwright E2E tests for a single spec file?

To run Playwright E2E tests for a single spec file, execute npm test scripts using npx Playwright commands to target specific test files, filter by test name, or perform debug runs with headed and UI mode for local inspection.

How do I debug failing Playwright E2E tests locally?

Debug failing Playwright E2E tests by running interactive UI mode or headed mode to reproduce failures, then inspect generated test-results artifacts and Playwright trace viewer reports to analyze console output and verify outcomes.

Can I align local Playwright test execution with GitHub Actions CI environments?

Yes, local Playwright test execution can mirror GitHub Actions CI environments by standardizing npm commands and environment configurations like BASE_URL, ensuring local findings match CI outcomes and artifact collection processes.

What environment variables do I need to run Playwright E2E tests on demand?

Running Playwright E2E tests requires configuring repository environment variables like BASE_URL alongside npm test commands, ensuring the test runner can properly execute end-to-end specs across local and CI contexts.

Why do my E2E tests fail inconsistently across local and CI environments?

E2E tests fail inconsistently due to misaligned execution configurations across local and CI environments; standardizing Playwright npm scripts, environment variables like BASE_URL, and artifact inspection ensures reliable outcome verification.

Does Playwright trace viewer work for analyzing test-results artifacts after E2E runs?

Yes, Playwright trace viewer works for analyzing test-results artifacts by guiding users to inspect generated reports and evidence artifacts, enabling detailed failure analysis and outcome verification after executing E2E test suites.