Start with the Open Test Step. Desktop and mobile use different Runner and Variant settings, so the page layout, viewport, and Element states can diverge even when the Flow is the same.

  1. Open the failing Test Case. Check the Open step’s Runner and Variant. Desktop usually uses Chrome (or Firefox/Edge) with a Desktop Variant. Mobile uses Simulated Device with a named device such as iPhone 14 Pro Max.
  2. Compare a passing desktop Run with the failing mobile Run. Confirm both open the same URL, then note which controls sit behind a hamburger menu or off-canvas layout on the smaller viewport.
  3. On the failing step, check whether the Element should be Displayed (shown on the page) or Visible (shown in the current viewport). Small screens often leave content off-viewport until you open a menu or scroll.
  4. Add Touch on the control that reveals the Element on mobile (for example the menu button), or use Scroll into view when the Element is already on the page but outside the viewport.
  5. If the mobile path should differ from desktop, add a Condition Test Step on Runner or Runner Variant, then put the mobile-only steps on that Flow Branch.
  6. Start a new Run on the Simulated Device Variant you care about and compare the screenshots with desktop.

If the page still fails after the layout matches, open Help in DoesQA and select Create new ticket. Include the Run ID.

Related docs: Open, Element states, Touch, Condition, Terminology.