Toolkit capability
Astro Safari and WebKit testing
Test Astro websites with Playwright WebKit, iPhone profiles, and native Safari in a pinned Xcode iOS Simulator.
Astro Safari and WebKit testing
Test Astro websites in WebKit and native mobile Safari.
A narrow Chromium viewport is not Safari evidence. Go for Launch combines automated WebKit touch flows with direct testing in a specifically identified iPhone Simulator.
What the process produces
06 concrete deliverables- 01Playwright WebKit iPhone suite
- 02Pinned Simulator device and UDID
- 03Touch navigation coverage
- 04Scroll-lock and modal checks
- 05Form and mobile-keyboard verification
- 06Blank-paint and overflow detection
Capability and requirements
What this workflow does, and what it needs.
Required inputs apply to this workflow. Conditional tools apply only when the project, platform, or chosen service needs them. A missing optional integration does not block unrelated Go for Launch checks.
Required for this workflow
Inputs and evidence
- Playwright WebKit with representative iPhone profiles
- macOS, full Xcode, and an installed iOS runtime for native Safari release evidence
- A staged candidate with representative routes and interactive flows
Only when applicable
Conditional tools and access
- Physical iPhone or iPad testing only when project policy or risk requires it
- Account credentials only for protected flows included in the test scope
- Remote device services only when local devices cannot cover the required environment
Automate representative WebKit flows
Cover route families, mobile navigation, dropdown destinations, modals, forms, fixed-header clearance, image rendering, long-page scrolling, and JavaScript errors.
Use native Safari for native failures
Boot one explicit Simulator device, open the staged hostname in Safari, and verify touch, first paint, address-bar destination, keyboard behavior, scrolling, and layout at the device level.
Repeat after production routing changes
Run live WebKit and native Safari smoke tests against the canonical hostname. This catches certificate, redirect, cache, and host-routing problems that staging cannot prove.