add-e2e-test

Add Playwright end-to-end tests with smoke gates and role-based assertions.

121|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/AgentSystemLabs/core --skill add-e2e-test-agentsystemlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-e2e-test
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/add-e2e-test
Command: npx skills add https://github.com/AgentSystemLabs/core --skill add-e2e-test-agentsystemlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents slow, flaky browser testing by guiding you to add a focused end-to-end Playwright test that hits the real user path only after confirming Playwright is set up and the dev server loop works.

Core Features & Use Cases

  • Playwright-aware E2E generation: Detects existing Playwright dependencies and config, then inherits baseURL/projects/auth/fixtures where available.
  • Hard-gated smoke test: Writes one minimal “app loads” test and requires it to pass before generating the real flow test.
  • Production-grade test style: Uses role- and label-based selectors, Playwright expect auto-retry assertions, and stable auth via storageState fixtures.
  • Auth support for real flows: Adds or references an auth-state setup when the flow requires a logged-in user.
  • Flake reduction: Instructs against fixed timeouts and non-retrying visibility checks, and validates stability via repeated runs.

Quick Start

Ask the AI to add an end-to-end Playwright smoke-and-flow test by telling it which page you start on, what you do there, and what visible result proves the flow worked.

Frequently Asked Questions about add-e2e-test

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

FAQPage Schema
How do I add a Playwright end-to-end test that verifies a real user flow through a running dev server?

To add a Playwright end-to-end test, you first ensure Playwright is set up and the dev server loop works, then generate a smoke test gate that must pass before writing role/label selector-based flow assertions with auto-retry checks.

Why does my Playwright E2E test keep flaking on fixed timeouts and non-retrying visibility checks?

Playwright E2E tests flake when using fixed timeouts and non-retrying visibility checks; you can reduce flakiness by using stable expect-with-auto-retry assertions and validating stability through repeated test runs.

How do I handle authentication state in Playwright for multi-step user journeys like sign-in or payments?

To handle authentication state in Playwright for multi-step user journeys, you add or reference an auth-state setup using storageState fixtures, allowing logged-in browser interactions to persist across the flow.

Can I use my existing Playwright config and baseURL when generating new E2E tests?

Yes, you can use your existing Playwright config because the generation process detects existing dependencies and inherits your configured baseURL, projects, auth, and fixtures where available.

What is a smoke test gate in Playwright and when do I need it before writing flow tests?

A smoke test gate in Playwright is a minimal "app loads" test that must pass before generating the real flow test, ensuring the development server and basic UI are observable before running complex browser interactions.

Does Playwright E2E testing work with role and label selectors instead of CSS selectors?

Yes, Playwright E2E testing works with role and label selectors instead of CSS selectors, utilizing production-grade test styles that target observable UI outcomes and improve test stability.