It was the only service where the docs actually had clear instructions and the only service where the automated tests actually worked. If for nothing else, I would suggest using their A notable mention is Appium<\/a>, which is perfect if you just want to test on your machine and your simulator. It’s open source and it even has support in AWS Device Farm.<\/p>\n Below are my notes about the tools\/services that I’ve tried.<\/p>\n As you’ve read in the TL;DR, my choice would be AWS Device Farm, so I’ll take a bit more space here and explain why I liked it the most, and I’ll showcase the simplest usage.<\/p>\n The official website is here<\/a> and the official documentation is here<\/a>.<\/p>\n There are two main ways to use AWS Device Farm:<\/p>\n The docs<\/a> for setting this up are really great and straight to the point.<\/p>\n Once you create your first project, you have to Then you have to select the Android\/iOS icon and upload your .apk\/.ipa file:<\/p>\n In the next step, you have to choose the test type that you would like to use. There are a lot of options, and as a starter (in case you don’t have your tests ready – we’ll cover these below in the Appium section) you can choose the In the next step you can select the various devices:<\/p>\n set some additional options and even pre-install some other apps:<\/p>\n After this, just review the settings and start the test. Tests will run in the background and in parallel on all the devices that you’ve set. Once this is done you will get an overview like this:<\/p>\n You can view the details of each run on the particular device:<\/p>\n You can view the screenshots, performance:<\/p>\n And you can even see the video of how the built-in test used your application:<\/p>\n Sure, these tests are not something on which we should rely on, and that’s why it’s great that we can write our own. In the next section, we’ll shortly cover Appium and why it’s so great for writing tests.<\/p>\n Appium<\/a> is a tool that makes automation possible for iOS and Android devices. It’s architected around four key principles:<\/p>\n Appium satisfies all these requirements in the following ways:<\/p>\n Few additional learning resources:<\/p>\n Once Appium is installed and running, click the proper OS icon (Droid\/Apple) and select the path to your compressed .ipa file (it is required that you zip the .ipa file):<\/p>\n One thing I had to set here as well was the Once this is set, you can simply click the Then you can click the Magnifier icon:<\/p>\n which will run your app in the simulator:<\/p>\n If you’re testing Hybrid apps, be sure to set the proper Context:<\/p>\n The best feature of Appium is that it lets you Record the tasks. To enable it, just click the Browserstack doesn’t support mobile app testing currently. Here’s the official thread<\/a>:<\/p>\n \n At this time, the mobile devices are available exclusively for cross-browser testing. Mobile app testing is on our roadmap for a later date.\n<\/p><\/blockquote>\n I’ve spent some time trying to get their solution to work as they popped up on most of the searches that I’ve done. However, I can’t say this was a pleasant experience as the docs seemed to be more like ‘Hey, we know how to do this, but if you want we can offer you our consulting support :\/’.<\/p>\n But, didn’t like their support as I’m still waiting for the answer to my question I’ve sent them. When I got the automated sales email, I followed up with the guy but again he said he couldn’t help me as he’s ‘only’ sales.<\/p>\n They allow you to upload your executable to their service, but only via terminal. They don’t have an interface for this on the site as AWS does, nor do they have an overview of the uploaded files.<\/p>\n You run all your tests from a script, and you can then see the screenshots and video of how the tests are interacting with your app:<\/p>\n However, the bottom line here is that I wasn’t too impressed with them.<\/p>\n I have also briefly looked at these services, but they didn’t seem intriguing enough to pursue any of them further.<\/p>\n So, yeah, as stated in the TL;DR AWS seems like the most viable solution to me right now. In case you have experience with some other solution, or you disagree with some of the conclusions that I’ve made, please let me know in the comments.<\/p>\n Also, if someone has extensive experience with writing and running tests on AWS Device Farm via Appium tests, I would love to get your feedback.<\/p>\n #Automated<\/a> #mobile<\/a> #testing<\/a> tools and services https:\/\/t.co\/rZpnBVQ9Fh<\/a> pic.twitter.com\/Yzbeg2ASya<\/a><\/p>\n — Nikola Bre\u017enjak (@HitmanHR) August 23, 2016<\/a><\/p><\/blockquote>\nRemote Access<\/code> option, as it’s really great because it gives you the ability to test your app on the particular device with the particular OS version in real time. This is definitely useful for when a user submits a bug, and you don’t have the actual device\/OS combination on which you could test.<\/p>\nLonger version<\/h1>\n
AWS Device Farm<\/h2>\n
\n
\n
\n
\n
Demo<\/h3>\n
Create a new run<\/code>:<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/LZuywbY.png\")
<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/iiDBZBz.png\")
<\/p>\nBuilt-in Fuzz<\/code> test.<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/8FVosGZ.png\")
<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/pC5rePM.png\")
<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/K7PAG09.png\")
<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/naYFJYF.png\")
<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/jJl6fn9.png\")
<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/XhtxBE7.png\")
<\/p>\nAppium<\/h2>\n
\n
\n
\n
Demo<\/h3>\n
![\"\"](\"http:\/\/i.imgur.com\/XmDLEQN.png\")
<\/p>\nBundleID<\/code>, as it didn’t work without it (BundleID can be found in your config.xml<\/code> file as the id<\/code> property of the widget<\/code> tag).<\/p>\nLaunch<\/code> button. Once the launching is done you’ll see something like the following in the logs:<\/p>\n[Appium] Appium REST http interface listener started on 0.0.0.0:4723<\/code><\/p>\n![\"\"](\"http:\/\/i.imgur.com\/7N2dN6v.png\")
<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/ZHfPZc8.png\")
<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/t8ZveHh.png\")
<\/p>\nRecord<\/code> button, navigate through the tree like structure and select the actions that you want to perform on the selected tags (Tap, Swipe, Shake, text inserting, etc.), and it generates the test code (in few different languages):<\/p>\n![\"\"](\"http:\/\/i.imgur.com\/Bshdhj0.png\")
<\/p>\nXamarin test cloud<\/h2>\n
\n
.ipa<\/code> file it threw an error: The .ipa file does not seem to be linked with Calabash framework.<\/code><\/li>\nCalabash<\/h3>\n
\n
Cucumber<\/h3>\n
\n
Browserstack<\/h2>\n
\n
Sauce labs<\/h2>\n
\n
![\"\"](\"http:\/\/i.imgur.com\/NNMSMHQ.png\")
<\/p>\nOther services<\/h2>\n
Firebase test lab<\/h3>\n
\n
eggPlant Mobile<\/h3>\n
\n
Soasta<\/h3>\n
\n
Squish<\/h3>\n
\n
Testmunk<\/h3>\n
\n
Keynote<\/h3>\n
\n
iOS only testing<\/h3>\n
\n
Windows only apps<\/h3>\n
\n
Miscellaneous<\/h2>\n
\n
Conclusion<\/h2>\n
\n