This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Jan 2019
1 / 6
Jan 2019
Jan 2019
hamena
Jan '19

Hello there!

I’m facing an iOS app with a really really big DOM in some screens. The DOM is formed by XCUITest elements (using XCUITest automationName capability).

Generally the whole execution is slow on iOS, but in those heavy screens the execution gets EXTREMELLY slow… Often the session timeouts while locating some element and test crashes.

I know XPath location strategy is very low on iOS, but even looking for an id (By.id) find for an element is really slow. From Appium inspector the behavior is the same.

I suspect I’m not facing this situation correctly, so there goes a bunch of questions:

  • XCUITest is currently the best automation engine to use for iOS?
  • There exists some capability like Android’s ‘ignoreUnimportantViews’ for DOM preprocessing? (Truncating the DOM to only on screen elements for example)
  • Which is the best location strategy? I assume it’s looking for id.
  • Principal causes of slowness iOS scripts?
  • Any suggestion for get my scripts quicker?

I’m using Appium server 1.9 and a iOS 11 system on a real device if it helps.

Thank you!

  • created

    Jan '19

  • last reply

    Jan '19
  • 5

    replies

  • 328

    views

  • 4

    users

  • 1

    like

  • 5

    links

mykola-mokhnach
Jan '19

Yes the only one

No, there is no such capability. XCUITest does not provide any information on which views are not important. Excluding elements by their visible attribute can bring multiple false positives

There are many

Read through the set of nice articles on Appium Pro dedicated to this topic. The first article can be found at https://appiumpro.com/editions/193