Slow interaction with Android apps - possible solution

[odklizec]

Hi guys,

I've recently started automating Android apps and I was shocked about the speed (slowness) of interaction with instrumented apps via spy and overall speed of playback. A simple test consisting of login, few touches and validations here or there and logout took about 18-20m! Plus it was incredibly slow to interact with the app UI, via Spy. Just today, I found an old post discussing similar issue. And sure enough, disabling "Full image comparison" in instrumentation settings helped also in my case! The same test now finished in 1.8-1.9m and interaction with UI via Spy is smooth, like working with desktop/web apps. I can finally track elements, without 30s or longer delays, between clicks in mobile app UI tree

FullImageComparison.png (33.03 KiB) Viewed 540 times

[dugovic.milan]

You are most likely aware of this, but when you run your tests over WiFi, not via USB it also speeds up you test execution. But anyhow, thanks for the hint. Much appreciated!

[odklizec]

Hi Milan,

Yes, I'm aware that wifi is supposed to be faster. However, it was not helpful in this particular case. It appears that if the instrumented app features camera functionality, this instrumentation flag dramatically slows the Ranorex/AUT interaction performance.

[mafi]

Hi,
I faced the same problem at my side as well, but that setting didn't help me so much.
It is true the Spy performances improved, but test running is still slow finding elements.
Perhaps it is just my feeling, but I think the speed gets worst elapsing time. I mean, the same object that searched at the beginning of the test can be found in some seconds, at the end of the test cannot be found at all. It seems that some kind of buffer overflows...
Anyone has the same problem?
Any suggestions?

[mafi]

I tried also to disable screenshots and Android OS automation options from plugin settings of solution, but nothing: speed slightly improves, but TS cannot finish, because latest test cases fail finding elements that at the beginning of the TS can be successfully found.
I also noticed that, trying to spy the device once failed TS, I can see the device, but no children in it.
I tried to refresh the connection during the test (Ranorex.Core.Remoting.RemoteServiceLocator.Service.GetByDisplayName(DeviceName).Reconnect(); and Ranorex.Core.Remoting.RemoteServiceLocator.Service.Refresh();) but it didn't help.
I do not know what's the problem; the main goal would be end the whole test suite and then increase performance if possible.
Is there anyone who can help with some suggestions?
Thanks.

[sstrand72]

I also am having issues with this. I have disabled web testing and full image comparison, along with always running over Wifi. But we are seeing it take a long time to identify elements on the screen. I also see a post about whitelisting the application in Ranorex to improve performance, however, it does not appear to apply to APKs on Mobile Devices/Tablets.

Any suggestions around this would be extremely helpful. Our tests can run for days and saving time is of the essence for us.

[odklizec]

Hi,

I'm afraid, it's impossible to suggest anything reliable without seeing the app under test. So I think you will have to contact directly Ranorex support about this? They will, of course need access to the apk.

The best I can suggest (without seeing, at very least, a Ranorex snapshot of the apk and example of slow xpath) is to improve the xpaths? I guess you will have to make the xpaths a bit more precise?