Open the failed Touch Test Step and read its responses first. DoesQA already waits for the Element and scrolls it into view before clicking, so start with what the run shows rather than adding more Wait or Scroll steps.

  1. Check the step responses for Element Existing, Element Displayed, Element Overlapped, and Element Disabled.
  2. Open the Element used by the step. Confirm it points at what you can see and click on the page, then check its Selector.
  3. If the Element does not exist, update the Selector or wait for the application state that creates it on the page.
  4. If the Element is not displayed, look for a hidden duplicate and use a Selector that matches the visible one.
  5. If the Element is overlapped, dismiss cookie banners, dialogs, sticky headers, or loading overlays. For stubborn overlays, open the Touch step advanced options and set Mode to Event.
  6. If the Element is disabled, wait for the application condition that enables it. Making the step slower only helps if that condition eventually happens.
  7. If it is inside a frame, add a Switch frame step before the Touch. Custom dropdowns that are not a real HTML select need Touch, not Select.

If the Touch still fails, open Help in DoesQA and select Create new ticket. Include the Run ID so support can open the same run.