mobile-browser-workflow-to-playwright

Translate mobile browser workflow markdown into Playwright E2E tests for Chromium.

23|1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/neonwatty/claude-qa-skills --skill mobile-browser-workflow-to-playwright
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-browser-workflow-to-playwright
Source: https://github.com/neonwatty/claude-qa-skills/tree/main/skills/mobile-browser-workflow-to-playwright
Command: npx skills add https://github.com/neonwatty/claude-qa-skills --skill mobile-browser-workflow-to-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates mobile browser workflow markdown files into Playwright E2E tests for CI using Chromium with mobile viewport, enabling teams to convert refined mobile flows into automated tests without rewriting from scratch.

Core Features & Use Cases

  • Converts each workflow in mobile-browser-workflows.md into a Playwright test structure with a mobile viewport (393x852) and hasTouch enabled.
  • Generates test scaffolding, helper utilities (swipe, pullToRefresh), and real/mobile-device-only test marks for permission dialogs or gestures that require physical devices.
  • Supports updating existing tests by diffing against the workflow file while preserving custom code blocks.

Quick Start

Run the translation workflow against /workflows/mobile-browser-workflows.md to generate e2e/mobile-browser-workflows.spec.ts.

Frequently Asked Questions about mobile-browser-workflow-to-playwright

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

FAQPage Schema
How do I convert mobile browser workflows to Playwright E2E tests?

Convert mobile browser workflows to Playwright E2E tests by translating workflow markdown files into test scaffolding with a mobile viewport (393x852) and hasTouch enabled for Chromium CI execution.

Can I use Playwright to automate mobile touch interactions like swipe and pull to refresh?

Playwright supports mobile touch interactions by generating helper utilities for swipe and pullToRefresh within the test scaffolding to meet mobile touch interaction requirements.

Does Playwright handle mobile browser steps that require real physical devices?

Playwright handles non-translatable mobile browser steps by marking device-specific interactions, such as permission dialogs or physical gestures, for real-device execution rather than forcing CI emulation.

How do I update existing Playwright tests when a mobile workflow changes?

Update existing Playwright tests by diffing the current test file against the updated workflow markdown, which preserves custom code blocks while applying the necessary step changes.

What is the best way to automate mobile workflows in CI without rewriting tests from scratch?

Automate mobile workflows in CI by translating refined workflow markdown into Playwright test structures, enabling teams to generate automated tests directly without rewriting from scratch.

What are the limitations of running mobile browser tests in Chromium with a mobile viewport?

Running mobile browser tests in Chromium with a mobile viewport cannot replicate physical device interactions, requiring real-device execution marks for steps involving permission dialogs or hardware gestures.