Libraries | Android | IOS | Server |
Yes | No | Calabash | |
Yes | Yes | Appium | |
No | Yes | Calabash iOS | |
Yes | Yes | Appium | |
Yes | No | UIautomator - Python wrapper | |
Yes | No | Robot Remote Server | |
Yes | Yes | Squishtest | |
Yes | No |
Ugh
1) I did go for Appium, but I did build my own library. And currently that library is not open source.
2) The question about real devices and emulated ones l, is a difficult one and it's question which does not have single correct answer. Example I must always use real devices because I work for a industry which doesn't allow to use any simulators. There are pros and cons for each side and the best advice I can give you is: Make small POC with both options and based on your experience choose the one which meets your needs best.
-Tatu
Send from my mobile
--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.
To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at http://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/d/optout.
Ugh
Unfortunately I do not recall what I did read.
Also it is impossible to recommend anything because your requirements are not clear.
But I can tell why I like Appium:
1) Appium is selenium, with a twist. Before Appium, I was somewhat familiar with selenium and the concept of the Appium is similar to selenium. That gave me familiar starting point.
2) Offered Python bindings
3) Support for native and hybrid applications.
4) Support for iOS and Android
5) Open source
-Tatu
Send from my mobile
--