Choose the device and the browser
Record the model, OS and browser for every mobile web check. A real-device browser session opens the website on physical Android or iOS hardware. A virtual device or viewport preview is useful for other checks, but it is a different test environment.
Follow one important journey all the way through
Start with a task such as finding a product, creating an account or submitting a request. Open menus, scroll through content, enter data and complete the task. Checking the full sequence gives more useful coverage than reviewing the first screen alone.
Watch the keyboard and changing screen space
Check whether the focused input and submit button remain reachable when the keyboard opens. Review sticky headers, modal dialogs, error messages and orientation changes. Test a short page and a content-heavy page if your product includes both.
Prepare private URLs and evidence
A staging site behind a firewall may need a provider tunnel before a remote device can reach it. Confirm that path in advance. Keep the page URL, browser, steps and screenshots with any issue; add recordings or developer-tool evidence when available.
Your testing checklist
- Open and close navigation with touch
- Complete forms with the on-screen keyboard
- Check errors without losing entered data
- Use browser back and forward through the journey
- Review portrait and landscape layouts
- Confirm the final action completes and shows clear feedback
A practical workflow
Choose the URL and user task
Identify the page, environment and task you want to validate.
Shortlist browsers and devices
Choose the mobile configurations supported by your product and audience.
Repeat the browser journey
Follow the same steps, record browser-specific differences and verify the fix.
Common questions
No. A mobile website test starts with a URL and browser configuration. Installed mobile app testing is a separate workflow.
A viewport preview is useful for layout checks. A physical-device browser check adds actual touch, keyboard and device/browser behavior to the test environment.
It may be possible through a provider tunnel when the site is private or on a local network. Include access restrictions and your staging setup when you request coverage.
Technical references
Official documentation for the underlying testing concepts. Available capabilities vary by provider and setup.
AWS Device Farm remote accessSauce Labs live cross-browser testingBrowserStack responsive Toolkit documentation