skills.rest
denisvmedia
denisvmediaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

inventario-e2e

Run and debug Playwright e2e tests against a local Go backend stack.

4|Updated Jun 10, 2023
Search Tags:#testing#debugging#playwright#frontend-backend#e2e-testing#docker-compose
One-click install
npx skills add https://github.com/denisvmedia/inventario --skill inventario-e2e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inventario-e2e
Source: https://github.com/denisvmedia/inventario/tree/main/.claude/skills/inventario-e2e
Command: npx skills add https://github.com/denisvmedia/inventario --skill inventario-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables you to run, reproduce, and debug Inventario's Playwright end-to-end tests locally, reducing time to diagnose flaky tests and PR failures.

Core Features & Use Cases

  • Orchestrate a local e2e stack (Go backend + frontend) and execute Playwright tests against it.
  • Reproduce failing tests quickly by launching the same environments used in CI and collecting artifacts such as test-results, traces, and reports.
  • Debug flaky or failing e2e scenarios with guided steps and artifact analysis for faster fixes.
  • Use cases include running single tests, reproducing CI failures, and debugging end-to-end flows in a local development setup.

Quick Start

Start the local Inventario e2e stack and run npx playwright test to reproduce or debug tests.

Frequently Asked Questions about inventario-e2e

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

FAQPage Schema
How do I run Playwright e2e tests locally for a full stack application?▼

To run Playwright e2e tests locally, orchestrate a local stack with the Go backend, frontend, and Playwright tooling, then execute the test runner to validate end-to-end flows against your local environment.

What is the best way to reproduce a failing e2e test from a CI pipeline locally?▼

Reproducing a failing CI e2e test locally involves launching the same docker-compose e2e stack used in CI, selecting the correct Playwright project, and collecting artifacts like traces and reports for diagnosis.

How do I debug flaky Playwright tests using test artifacts?▼

Debugging flaky Playwright tests requires analyzing generated test-results, traces, and reports to identify intermittent failures, using guided steps to inspect the end-to-end flow and apply fixes.

Do I need a local Go server and frontend to execute end-to-end testing?▼

Yes, executing end-to-end testing requires a local stack running the Go backend server, frontend, and Playwright tooling to properly validate frontend-backend integration scenarios.

Can I run a single Playwright test instead of the entire e2e suite?▼

Yes, you can run a single Playwright test by configuring the test runner to target specific e2e scenarios, allowing you to quickly reproduce individual failures without executing the full suite.

Related Skills

Explore More Software Engineering Skills→
pward17pward17

deps

Audit and update frontend and backend dependencies with Docker-based workflows.

Community
Intermediate
ProjectEuropaProjectEuropa
4

e2e-debug

Diagnose failing Playwright E2E tests and CI regressions with repair steps.

Community
Advanced
williamzujkowskiwilliamzujkowski
6

Integration Testing Designer

Design integration test plans for multi-service interactions across databases, APIs, and message buses.

Community
Advanced
fgarofalo56fgarofalo56
6

testing

Run unit, integration, and E2E tests with pytest, Jest, Cypress, and Playwright.

Community
Advanced