skills.rest
sizukutamago
sizukutamagoCOMMUNITY
Explore all skills by this author →
GitHub

e2e-test

Observe live UI with browser-operator and generate Playwright Test code.

Updated Mar 29, 2026
Search Tags:#automation#testing#e2e#playwright#quality-assurance#test-design#browser-operator
One-click install
npx skills add https://github.com/sizukutamago/claude-code-harness --skill e2e-test-sizukutamago
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/sizukutamago/claude-code-harness/tree/main/.claude/skills/e2e-test
Command: npx skills add https://github.com/sizukutamago/claude-code-harness --skill e2e-test-sizukutamago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

browser-based end-to-end test design can be error-prone if testers guess selectors or skip real UI observation. This skill provides a structured workflow to observe a live UI with browser-operator and produce robust Playwright Test code.

Core Features & Use Cases

  • Observe UI with browser-operator to understand layout, controls, and navigation.
  • Design test cases (happy path, validations, transitions, edge cases) aligned with observed behavior.
  • Implement Playwright Test code iteratively with human-in-the-loop validation and automated execution.

Quick Start

Start by pointing the browser-operator at the target URL to observe UI, then design test cases and implement Playwright tests to achieve green results.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I generate reliable Playwright tests without guessing UI selectors?▼

Design Playwright tests by observing real UI behavior with browser-operator to understand layout, controls, and navigation, then implement robust selectors and synchronization for accurate end-to-end coverage.

What is the best way to design end-to-end tests for new UI features?▼

Design end-to-end tests for new UI features using a browser-operator guided workflow to observe the live application, then create happy path, validation, and edge case tests aligned with actual observed behavior.

Do I need a browser-operator to write Playwright test code for existing apps?▼

Yes, a browser-operator is required to observe the existing app's UI and navigation, ensuring accurate test coverage across multiple screens and user flows before implementing the Playwright test code.

Can I cover edge cases and validations when automating Playwright tests?▼

Yes, you can cover edge cases and validations when automating Playwright tests by iteratively designing test cases based on observed UI behavior and validating them with human-in-the-loop automated execution.

Why does my Playwright test fail when I skip real UI observation?▼

Playwright tests fail when skipping real UI observation because guessing selectors or ignoring actual layout and transitions leads to error-prone tests; observing the live UI ensures robust selectors and synchronization.

Related Skills

Explore More Software Engineering Skills→
simonwjacksonsimonwjackson

se-polish-beta

Start a development server and open the feature in a browser.

Community
Advanced
Vivekmano27Vivekmano27

webapp-testing

Automate end-to-end web application testing with Playwright and Page Object Model.

Community
Advanced
vladolaruvladolaru
6

browser-interaction

Automate browser clicks, form filling, and screenshots via Chrome DevTools MCP or Playwright.

Community
Advanced
figuedmundofiguedmundo

senior-qa

Generates test suites, analyzes coverage, and scaffolds E2E tests for ReactJS, NextJS, and NodeJS.

Community
Advanced