Include device family and OS version
An iPhone check does not cover every iPad layout or OS configuration. Choose the Apple device families your app supports and record the exact version under test. Treat tablet-specific layouts as their own coverage decision.
Confirm build and signing requirements early
Physical-device cloud testing commonly uses an IPA build. Installation, provisioning and any provider re-signing can affect what is required before a session. Tell the provider about signing constraints and features tied to your app's configuration before arranging access.
Check the points where the system joins the journey
Review permission prompts, app backgrounding, return to the previous task and keyboard interaction. On larger screens, check spacing, navigation and orientation changes. Use test accounts and agreed test data to make these steps repeatable.
Keep app tests separate from Safari tests
An installed app and a website open in Safari are different targets. An app test needs its build and app workflow; a website test needs the URL and browser configuration. A product that includes both should keep both checklists.
Your testing checklist
- Verify the intended build installs and opens
- Review onboarding and sign-in
- Allow and deny permissions used by the app
- Check keyboard overlap around important inputs
- Rotate supported screens on iPhone and iPad
- Retest a reported issue on its exact model and OS
A practical workflow
Confirm the app requirements
Prepare the build version and explain any signing or provisioning constraints.
Choose phone and tablet coverage
Prioritize the iPhone, iPad and OS configurations that matter to your users.
Capture a repeatable result
Keep steps, expected behavior, actual behavior and the tested build together.
Common questions
Do not assume a simulator build is suitable. Physical-device cloud workflows commonly use IPA files, while simulator workflows have different requirements. Confirm the accepted package with the service.
Include it when your app supports iPad or your audience uses it. The larger screen and orientation changes can introduce journeys and layouts that deserve separate checks.
Appium and XCTest-related workflows are common examples of iOS automation. Exact framework support and build requirements depend on the service, so include them in your request.
Technical references
Official documentation for the underlying testing concepts. Available capabilities vary by provider and setup.
AWS Device Farm test frameworksBrowserStack iOS testingSauce Labs Appium tests on real devices