Camera preview mirroring and orientation: a test checklist
Separate preview appearance, captured output and state continuity with a reproducible camera test plan.
Start with a subject you can verify
Place an asymmetric target, such as a card reading LEFT with an arrow, in the frame. Record the selected camera, preview orientation, mirroring choice and capture format. Inspect both the preview and the saved output; matching appearance is a product choice that must be explicit.
Exercise one transition at a time
Take a baseline image, rotate, and repeat. When the supported Duo environment is available, repeat across opening/closing and supported camera-direction changes. Confirm framing and the expected subject remain correct. Apple’s camera talk discusses virtual front cameras, direction handling and preview rotation; validate any API against the SDK you actually build with.
Test continuity independently of appearance
Start a recording, perform a supported transition and stop it. Verify playable output, duration and audio continuity using the resulting file and app logs. For photos, confirm a single intended capture completes. A pretty preview cannot demonstrate that capture state survived.
Review what the subject can see
For an app exposing content on another display, inspect that display from the subject’s side. Test private controls, notifications within your UI and sensitive content. Include denial of camera permission, interruptions and background/foreground recovery. These are proposed review cases, not claims of automatic coverage.
Write an evidence record
Record the commit, SDK, runtime/device, starting state, exact transition, expected behavior and actual result for each case. Mark unexecuted cases Not run. Use the downloadable plan below as a starting point and the Mac runner documentation for the existing evidence import workflow.
Sources and limits
Our calculations and proposed test steps are independent analysis. Follow the original documentation for SDK-specific behavior.