Add a local iPhone Duo end-to-end check - #36
Draft
janicduplessis wants to merge 2 commits into
Draft
janicduplessis wants to merge 2 commits into
janicduplessis wants to merge 2 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
pnpm run e2e:ios(e2e/ios.mjs), a local-only counterpart toe2e:androidthat checks the iPhone Duo behavior recorded in the 0.2.0 verification doc, using only the example's on-screen text. No library changes, no logging patch, and no workflow in the repo.The script builds and installs the example in Release (no Metro), reuses or creates its own
Reserved Regions E2EDuo simulator (or takesE2E_IOS_UDID), opens the hinge to 130° withagent-device fold, and asserts:It uses tolerances rather than the exact Duo numbers, and reads each state only after two consecutive snapshots match, because a fold dispatches several intermediate payloads.
Fails fast before building unless it finds Xcode ≥ 27.1, the iPhone Duo device type, an iOS ≥ 27.1 runtime that supports it, and agent-device ≥ 0.21.12 (needed for
fold). The message names what to install.docs/workflow.mdgets an "Automated iOS check" section, and the verification doc gets a one-line pointer to the script.@janic/duo-verifystays: the verification doc still citesa9b3f08on that branch.Test plan
pnpm run e2e:iosonxcode-27-xlargewith Xcode 27.1 beta and a downloaded iOS 27.1 runtime: run 35926702428, 5.4 min for the script and 9m46s for the job. It printed the same values as the verification doc, for example: