🧩 The Edge Case | It Passed in Mobile View. What About a Real Phone? ✅

Sponsor Spotlight • Level 1

Partner with QA Testing Jobs to feature your tools, platforms, or services to thousands of testers every week.

Hi there,

Your form looks good in mobile view. The buttons fit, the layout stacks neatly, and the automated test passes.

Then someone opens it on their phone. The keyboard covers the next field. An error message appears outside the visible area. Switching apps midway through the form loses their progress.

A smaller browser window is useful evidence. Real-device testing adds another layer.

There’s a timely reason to revisit this: Perfecto’s latest release adds beta Playwright support for web applications on real iOS devices, using Playwright 1.62 and JavaScript or TypeScript.

But you can try the exercise below with a phone and your existing test environment.

Pick one important journey, such as signing in, completing a purchase, or submitting a job application. Then check these five things:

1. Open the keyboard. Tap every input, including the last field. Can you see what you’re typing, reach validation messages, and continue without dismissing the keyboard repeatedly?

2. Trigger an error. Submit an empty required field or an invalid value. Is the problem visible and understandable? Can you reach the field and correct it?

3. Leave and return. Switch to another app to retrieve a code or copy some text, then come back. Check whether your progress, focus, and session behave as expected.

4. Interrupt the connection. In a test environment, disconnect briefly before submitting, then reconnect and retry. Look for lost input, duplicate submissions, and misleading success messages.

5. Use the phone’s navigation. Try Back, rotate the device, and scroll through the whole journey. Check for unexpected resets, hidden controls, or content you can no longer reach.

Make the result useful: record the device, OS, browser, exact steps, and expected versus actual behaviour. Include a short recording where it helps, and compare the same steps with your emulated mobile test.

If you’re building your testing portfolio, this makes a focused case study. If you lead a team, use the findings to decide which journeys deserve regular real-device coverage.

One journey. One phone. Better evidence about the experience your users actually get.

Yours in testing,
Farid Vaswani

Community Partner

Have a QA community, course, or event to promote? Reply to reserve this feature placement.