Does this skill work with production or staging environments?

No, this skill is specifically designed for local development environments to ensure tests run against controlled, local backend and database instances.

Why is the 'No Mock Data' policy important?

Using real API calls and databases ensures that your integration tests reflect the actual behavior of your system, catching bugs that mocks often hide.

Can I use this for manual UI debugging?

Yes, by using the --browser flag, the skill switches to Claude in Chrome mode, allowing for real-time interaction and manual exploration of the UI.

How does the skill handle services that aren't running?

It includes a health check phase that uses curl to verify your API and frontend ports are active before attempting any test execution.

Local E2E Testing Workflow

Name: Local E2E Testing Workflow
Author: devnogari

bydevnogari

•

Seguridad y Pruebas

Automates full-stack E2E testing by integrating local frontend and backend services without using mock data.

Acerca de

This skill facilitates highly realistic testing environments by connecting your local frontend directly to a live local backend and database. By enforcing a strict 'No Mock Data' policy, it ensures high-fidelity verification of API calls, authentication flows, and database interactions. It supports automated E2E test execution using popular runners like Playwright or npm scripts, while also offering an interactive mode via Claude in Chrome for manual UI exploration and real-time debugging.

Características Principales

No-mock policy for real API and database integration
Automated service health checks for backend and frontend
Interactive browser testing via Claude in Chrome
2 GitHub stars
Automated E2E test execution with standard runners
Detailed network request and console log inspection

Casos de Uso

Running full-stack regression tests against a local backend
Verifying complex authentication flows with real database records
Debugging UI-backend interactions in a live browser session

Acerca de

Características Principales

No-mock policy for real API and database integration
Automated service health checks for backend and frontend
Interactive browser testing via Claude in Chrome
2 GitHub stars
Automated E2E test execution with standard runners
Detailed network request and console log inspection

Casos de Uso

Running full-stack regression tests against a local backend
Verifying complex authentication flows with real database records
Debugging UI-backend interactions in a live browser session