Appium Android really slow compared to when I run same test in Selendroid mode.

[Kirsty D]

Hi,

Selendroid is really fast compared to Appium - which is significantly slower. For example I am running the same test on the same emulator in appium mode and selendroid mode. In Selendroid, it takes around 1 min 30 secs to run the test. It whizzes through like a normal website Selenium test.  In normal appium mode it takes over 4 minutes. Is there any reason for this? It seems Selendroid works really well with Selenium but Appium, while it works, takes seconds longer to perform each Selenium action. Is it because of the different automation strategy behind them?

So for example I just want to check for buttons on a page which has fully loaded - in Selendroid it zooms through locating all the buttons - in Appium it takes around 3 seconds to locate each button.

Anything which uses a Selenium action seems to take a painfully long time e.g:

element.isEnabled()

element.click()

element.isDisplayed()

and the actual location of the elements themselves. . .

Would be great to understand why there is such a difference and are there plans to address this? Or is this out of Appium control because of the Android automation strategy behind it?

Thanks,

Kirsty

[bootstrap online]

I think turning on compression in uiautomator mode will have a
significant impact on speed. That's something we're looking into once
XPath is fixed up.

> --
> http://appium.io
> ---
> You received this message because you are subscribed to the Google Groups
> "Appium-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to appium-discus...@googlegroups.com.
> Visit this group at http://groups.google.com/group/appium-discuss.
> For more options, visit https://groups.google.com/d/optout.

[Kirsty D]

That's great. So something to look out for in the future (i.e. not some setting I can set now through Appium?)

Thanks,

Kirsty

[bootstrap online]

It's not currently possible to set because of the existing xpath
implementation. If you want to try it anyway, you could make a custom
build of the Java server, look for NotImportantViews.discard, and
ensure it's always true.

I expect this to be configurable in an upcoming appium release.

[Jerald vinoth kumar]

Hi Kirsty,

I would like to run my test in Selendroid mode. Could you please let me know the capabilities you are using?

Is the below capability enough to switch to Selendroid mode?

capabilities.setCapability("automationName","Selendroid");

Thanks,

Jerald

[Kirsty D]

Hi Jerald,

Yes that should be all you need (along with all the standard capabilities.)

I found that I had to run the a test first on a new device (I am using emulator) - would get some server side error. Then after that the device would be ok and I can run in selendroid or normal appium mode.

Kirsty

[Kirsty D]

Hi Bootstraponline,

Just out of interest what is the xpath stuff going to do? On the whole I find Appium more reliable in terms of automation than Selendroid. For example in Selendroid it can locate elements that are not displayed (presumably because they are loaded into the view) but even if I check their isDisplayed and isEnabled properties it says they are both displayed and enabled - so I cannot reliably check that something does not appear on the page.  For Appium it correctly only shows elements currently in view. The xpath changes being made are not going to affect this?

Thanks,

Kirsty

[Priya]

Hi Kristy,

Could you please guide me through setting up Appium?

I went through the documentation and installed all the necessary softwares. When I connect the device (API level 19), I don't see anything on the Appium screen. I am unable to proceed further from there.

Could you please guide me to any site with that shows the sequence of steps.

Thank you very much.

-Priya

[Himanshu]

Hi Kristy

Can you please look out for my issue in the link given below
https://groups.google.com/forum/#!topic/appium-discuss/6Gqbh6ZUrgQ