write-e2e-test

Automate end-to-end UI validation for agentconfig.org using Playwright with TypeScript.

7|3|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/agentconfig/agentconfig.org --skill write-e2e-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-e2e-test
Source: https://github.com/agentconfig/agentconfig.org/tree/main/.github/skills/write-e2e-test
Command: npx skills add https://github.com/agentconfig/agentconfig.org --skill write-e2e-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create maintainable Playwright E2E tests that mirror project patterns for UI components and user interactions, ensuring regression safety.

Core Features & Use Cases

  • Provides guidance on test file locations, structures, and common patterns for navigation, themes, responsive behavior, and accessibility checks.
  • Enables teams to validate component behavior, interactions, and page flows across breakpoints and themes.

Quick Start

Run the Playwright tests located under site/tests/e2e to validate new features and UI changes.

Frequently Asked Questions about write-e2e-test

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

FAQPage Schema
How do I write Playwright E2E tests for web UI components and navigation?

Playwright E2E tests for web UI components are written using TypeScript under the site/tests/e2e directory. Tests locate elements by roles, labels, and text to validate navigation, component behavior, and user interactions deterministically.

What's the best way to validate responsive behavior and themes in Playwright E2E testing?

Responsive behavior and themes in Playwright E2E testing are validated by applying test patterns that check page flows across breakpoints and themes. This ensures UI components render correctly and maintain regression safety during feature releases.

Do I need TypeScript to run Playwright E2E tests for regression checks?

TypeScript is required to run these deterministic Playwright E2E tests for regression checks. The project structure depends on TypeScript to maintain reliable test patterns for navigation, accessibility checks, and component validation.

How do I structure E2E test files for web automation to ensure maintainability?

E2E test files for web automation are structured by mirroring project patterns within the site/tests/e2e directory. This organization maintains regression safety by keeping navigation, component, and responsive behavior tests aligned with site features.

Can I use Playwright to automate accessibility checks for web UI interactions?

Playwright can automate accessibility checks for web UI interactions by applying test guidance that validates component behavior and page flows. It locates elements by roles and labels to ensure accessible user interactions across breakpoints.

Why should I locate elements by roles and labels instead of CSS selectors in E2E testing?

Locating elements by roles and labels in E2E testing ensures tests remain maintainable and accessible. This approach validates actual user interactions and component behavior deterministically, rather than relying on brittle CSS selectors that break during UI changes.