skills.rest
danielkhigay
danielkhigayCOMMUNITY
Explore all skills by this author →
GitHub

e2e

Automate end-to-end testing of Gaz features against the dev server using Playwright MCP.

Updated Feb 19, 2026
Search Tags:#testing#e2e#playwright#session-management#qa-automation#test-orchestration#dev-api
One-click install
npx skills add https://github.com/danielkhigay/gaz --skill e2e-danielkhigay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/danielkhigay/gaz/tree/main/.claude/skills/e2e
Command: npx skills add https://github.com/danielkhigay/gaz --skill e2e-danielkhigay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing of Gaz features against the running dev servers using Playwright MCP and the dev API shortcuts to ensure correct behavior after implementation.

Core Features & Use Cases

  • Orchestrates single-feature and parallel e2e runs to validate acceptance criteria across multiple requirements.
  • Manages test data with the dev API (users, sessions, votes) and isolates each test scenario for reliability and repeatability.
  • Generates per-criterion PASS/FAIL/SKIP reports and supports cleanup of test artifacts post-execution.

Quick Start

Provide a requirement file path or describe a feature, then launch the e2e tests against the live dev servers.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I automate end-to-end testing against a running dev server?▼

End-to-end testing is automated by orchestrating Playwright against the live dev server while using dev API shortcuts for automated user and session setup. It validates feature behavior after implementation and generates per-criterion results.

How do I manage test data and sessions for QA automation?▼

Test data management for QA automation is handled through the dev API, which creates and isolates users, sessions, and votes for each scenario. This ensures reliability and repeatability, with automated cleanup of test artifacts post-execution.

Can I run parallel e2e tests across multiple requirements?▼

Yes, you can run parallel e2e tests across multiple requirements. The orchestration supports both per-feature and parallel test runs to validate acceptance criteria simultaneously against the dev server.

What is the best way to verify feature acceptance criteria after implementation?▼

The best way to verify feature acceptance criteria is to launch automated e2e tests using Playwright. Provide a requirement file path or feature description, and the system reports PASS, FAIL, or SKIP for each criterion.

Does this e2e testing approach require a running dev server?▼

Yes, this e2e testing approach requires a running dev server. It automates feature verification by executing Playwright test plans directly against the live development environment and managing test data via the dev API.

Related Skills

Explore More Software Engineering Skills→
thisisryanswiftthisisryanswift
2

ce-polish-beta

Start a local dev server and open the feature in a browser.

Community
Intermediate
dangelesdangeles
6

completion-verifier

Verify task completion against acceptance criteria and generate a verification report.

Community
Advanced
Dragoon0xDragoon0x
4

qa

Generate stack-matched Playwright smoke tests with runner scripts.

Community
Intermediate
Svenja-devSvenja-dev
38

e2e-testing

Automate end-to-end browser testing for web applications with Playwright MCP.

Community
Intermediate