Repository navigation
test(ios): committed ASWebAuthenticationSession fixture + CI lane #2449
Description
Purpose. #2448 shipped in-place capture/drive of com.apple.SafariViewService sign-in sheets, live-validated with a throwaway probe app. Give it a committed fixture and CI coverage on the real path.
Required behavior.
- Add an
expo-web-browseropenAuthSessionAsync(orAppAuth) flow toexamples/test-appthat opens a web sign-in sheet against a local/bundled IdP page (email + password + submit → callback scheme). - Add an iOS smoke or Maestro replay lane that drives it semantically:
wait label="LOGIN"→press role=textfield+type→fill role=securetextfield→press role=button label="LOGIN"→ assert return to app.
Observable completion. The lane runs in CI on the shipped runner and fails if the sheet is not served (regression guard for the route bypass + runner serve).
Dependencies. Builds on #2448 (registry, runner serve, route probe already landed).
Activity
thymikee commentedon Sep 10, 2026
Sequenced behind #2448 deliberately: this lane asserts the semantic sign-in flow (
wait label="LOGIN"→press role=textfield+type→fill role=securetextfield→ submit), which only passes once the in-place serve lands. Building it againstmainfirst would land a red lane.Plan when #2448 merges: stack the fixture + lane on it, then validate live on a simulator. Note the cold-start caveat — the first capture after a cold runner can return 0 nodes (pre-existing, tracked as #2343), so the lane should
wait stable/wait <element>before reading the sheet rather than snapshotting immediately.