playwriter-spec

Reproduce flaky end-to-end UI test flows with Playwright-style browser debugging.

198|19|Updated Sep 15, 2025

Search Tags:#manual testing #playwright #ui automation #test flakiness #e2e debugging #playwright flows

Ready to run

npx skills add https://github.com/iterate/iterate --skill playwriter-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: playwriter-spec
Source: https://github.com/iterate/iterate/tree/main/.opencode/skills/playwriter-spec
Command: npx skills add https://github.com/iterate/iterate --skill playwriter-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an app’s end-to-end test is flaky or actively changing, it can be hard to reproduce the exact UI behavior and understand why assertions fail.

Core Features & Use Cases

Manual E2E execution: Run the same user journey steps in Playwright/Playwriter-style flows to observe real UI behavior.
Faithful workflow mapping: Extract test intent into a reproduce/verify sequence (observe → act → observe) while flagging deviations.
Actionable debugging output: Capture evidence, timing, blockers, and concrete fixes when the outcome diverges from the test.

Quick Start

Use the skill by running your OS app E2E tests from apps/os with your environment base URL, then translate the failing test’s steps into a manual Playwriter session for in-browser debugging.

Frequently Asked Questions about playwriter-spec

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

FAQPage Schema

How do I debug flaky Playwright E2E tests manually?▼

Debug flaky Playwright E2E tests by extracting the failing test's journey, setup, and assertions, then executing observe-act-observe steps in-browser to reproduce real UI behavior and identify assertion deviations.

What causes UI test flakiness in end-to-end flows?▼

UI test flakiness in end-to-end flows often stems from timing issues and changing user journeys. Manual reproduction using Playwright-style debugging helps observe real UI behavior and identify where product signals diverge from assertions.

How do I manually reproduce an E2E test flow in the browser?▼

Manually reproduce an E2E test flow by reading the full target test, extracting its journey and assertions, and running the steps in-browser. Observe UI behavior at each step, preferring product signals over sleeps, to generate a pass/fail summary.

Can I run Playwright E2E debugging for tests in per-app directories?▼

Yes, you can debug Playwright E2E tests located in per-app directories. Run your app E2E tests from the apps/os directory using your environment base URL, then translate the failing test steps into a manual debugging session.

What is the best way to fix failing E2E UI assertions?▼

The best way to fix failing E2E UI assertions is to manually run the user journey in-browser, capture evidence and timing blockers during observe-act-observe steps, and produce a summary with concrete fixes based on product signals.

When should I not use manual E2E test execution?▼

You should avoid manual E2E test execution when the UI journey is stable and not actively changing, as the process requires reading full target tests and translating steps, making it less efficient for consistent, non-flaky automation.