local-testing

Run end-to-end tests locally against a live backend and frontend with Playwright.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/devnogari/devnogari-claude-plugins --skill local-testing-devnogari
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-testing
Source: https://github.com/devnogari/devnogari-claude-plugins/tree/main/plugins/feature-workflow/skills/local-testing
Command: npx skills add https://github.com/devnogari/devnogari-claude-plugins --skill local-testing-devnogari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers run end-to-end tests locally against a real backend and frontend stack without relying on mocks, enabling realistic validation of features before deployment.

Core Features & Use Cases

  • Default E2E testing against local services with automatic server health checks.
  • Browser-mode testing with Claude in Chrome using the --browser flag for real-time interactions.
  • Guided workflows for server checks, test execution, and result reporting via Playwright.

Quick Start

To begin, use one of the following commands:

  • /local-testing [test-name]
  • /local-testing [page-path] --browser

Frequently Asked Questions about local-testing

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

FAQPage Schema
How do I run E2E tests locally against a live backend without mock data?

You can run E2E tests locally against a live backend without mock data by executing test orchestration scripts via npm, yarn, or pnpm. This Skill automates server health checks and validates feature integration against your real stack before reporting results through Playwright.

Can I run Playwright E2E tests with real-time browser interactions?

Yes, you can run Playwright E2E tests with real-time browser interactions by using the --browser flag. This enables Claude-in-Chrome browser support, allowing you to validate UI interactions against your local frontend and backend services dynamically.

What is the best way to validate feature integration before deployment?

The best way to validate feature integration before deployment is running local E2E tests against a real stack. This approach uses automatic server health checks and Playwright reporting to confirm your server and frontend work together without relying on mock data.

Do I need mock data to test UI interactions against my local development stack?

No, you do not need mock data to test UI interactions against your local development stack. This Skill enables testing against a live backend and frontend, providing realistic validation of features and server health without the overhead of generating mock data.

How does server health checking work before running local E2E test orchestration?

Server health checking works by verifying that your local backend and frontend services are running before executing E2E test orchestration. This ensures that your Playwright tests interact with a live stack, preventing false failures from unstarted services.

What are the limitations of using Claude-in-Chrome for E2E testing?

Claude-in-Chrome for E2E testing is an optional browser-mode feature triggered by the --browser flag. It is limited to real-time interaction scenarios within your local environment and relies on your existing Playwright test setup and live server health checks to function correctly.