iOS Workflow to Playwright FAQs

Question 1

How are iOS-specific gestures like 'swipe' handled?

Accepted Answer

The skill generates custom TypeScript helper functions that simulate touch events and mouse movements to approximate mobile gestures within the Playwright environment.

Question 2

Can it update existing test files or does it overwrite them?

Accepted Answer

The skill includes a reconciliation phase that parses existing test files to identify new, modified, or removed workflows, ensuring your test suite stays in sync with your documentation.

Question 3

Which selectors does the skill prioritize for mobile elements?

Accepted Answer

It follows a strict hierarchy favoring data-testids and ARIA labels first, followed by semantic roles and mobile-specific CSS classes to ensure maximum test stability.

Question 4

Does this skill require a physical iPhone or iOS Simulator?

Accepted Answer

No, it generates tests designed to run in Playwright's WebKit engine using mobile viewport emulation, making them ideal for standard CI/CD runners without needing macOS-specific hardware.

Question 5

What happens if a workflow step requires native iOS permissions?

Accepted Answer

Steps involving native system dialogs (like camera or location permissions) are automatically wrapped in 'test.skip' blocks with notes explaining that they require a real iOS Simulator to execute.

iOS Workflow to Playwright

Key Features

Use Cases

iOS Workflow to Playwright

Key Features

Use Cases