Skip to main content

Testing Mobile Apps in the Cloud - Product Comparison

Cloud testing is raising, especially for mobile automated testing it is even going faster. Basically, cloud testing means that an application is installed on real devices or simulators/emulators that are hosted in one of the cloud testing services providers. These devices are maintained by the service providers and promise to be up and ready for service with a subscribed contract so no need to tackle these kinds of stuff for the sake of focusing on building the right product with well-tested features. In this post, I want to share some info about main mobile cloud solutions in the market.

 

PRODUCT PRICE SUPPORTED TOOLS
AWS Device Farm
  • Pay as you go
    • $0.17 / DEVICE MINUTE
    • Test on any of our devices in parallel and pay just for what you use
    • Your first 1000 minutes are free*
  • Unlimited testing
    • STARTS AT $250.00 / MONTH
    • Test as much as you want each month for a flat rate
  • Private devices
    • STARTS AT $200/MONTH
    • Test on dedicated devices deployed exclusively for your account
  • Appium
    • Java (TestNG)
      • Currently, Device Farm supports Java 8 for running Appium Java tests. 
    • Java (JUnit)
      • Currently, Device Farm supports Java 8 for running Appium Java tests. 
    • Node.JS
      • You can use any Node.js version when you run Appium Node.js tests on Device Farm. Specify the Node.js version in the test spec YAML file. 
    • Python
      • In standard mode, Device Farm supports Python version 2.7 for running tests. In custom mode, both Python 2.7 and Python 3 (3.7) are available. 
    • Ruby
      • You can use any Ruby version when you run Appium Ruby tests on Device Farm. Specify the Ruby version (for example, 2.5.1) in the test spec YAML file.
  • Calabash
  • Espresso
  • XCUITest
  • UI Automater
Firebase Test Lab
  • Free
    • Virtual Device Tests $1/device/hour 
    • Physical Device Tests $5/device/hour
  • pay as you go
    • Virtual Device Tests 10 tests/day
    • Physical Device Tests 5 tests/day
  • Test Tools
    • Espresso
    • UI Automator 2.0 
    • XCUITest
App Center / Visual Studio App Center
  • 30 days free trial
    • For 30 days, you will be able to test your app on more than 450 device configurations.
    • With the trial, you can test your app on 1 test device concurrency with unlimited device hours.
  • Run unlimited, faster builds
    • Ship your app faster with multiple builds running in parallel.
    • Each build you pay for comes with unlimited build time, ensuring all builds run and complete.
    • $40/month per build concurrency
  • Standard Test Plan
    • Each device concurrency comes with 30 device hours.
    • $99/month per device concurrency
  • Enterprise Test Plan
    • Unlimited test hours on thousands of real devices and OS configurations.
    • Each device concurrency comes with unlimited device hours.
    • $499/month per device concurrency
  • Test Tools
    • Appium 
    • Espresso
    • XCUITest
    • Calabash - no support anymore
Browserstack
  • App Automate
    • 199$ / month - 1 parallel
    • 399$ / month - 2 parallel
    • 999$ / month - 5 parallel
  • Live Testing
    • 29$ / month - 1 parallel 
    • 99$ / month - 2 parallel 
    • 199$ / month - 4 parallel
  • Test Tools
    • Appium 
    • Espresso 
    • XCUITest
SauceLabs
  • App Automation
    • 399$ / month - 2 parallel
      • Unlimited automated testing minutes
    • 799$ / month - 4 parallel
      • Unlimited automated testing minutes
  • Live Testing
    • 49$ / month - ? parallel
  • Test Tools
    • Appium 
    • Espresso 
    • XCUITest
Kobiton
  • App Automation
    • 40$ / month 
      • Unlimited parallel 
      • 500min /month
    • 167$ / month 
      • Unlimited parallel 
      • 2000min /month
  • Live Testing
    • Included
  • Test Tools
    • Appium 
    • Espresso 
    • XCUITest
    • Scriptless automation

Let's look at the high-level to detail by mindmap picture



Popular posts for software testing and automation

Selenium Error "Element is not currently interactable and may not be manipulated"

Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last):   File "D:\workspace\sample_project\sample_run.py", line 10, in <module>     m.login()   File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login     driver.find_element_by_id("id_username").clear()   File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\r

Change Default Timeout and Wait Time of Capybara

One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg

Page-Object Pattern for Selenium Test Automation with Python

Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part.   The last part is related to asserting your test cases against to the

Create an Alias for Interactive Console Work: Selenium and Capybara

If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each.  This post is for Windows machines, if you are using Unix-like see   this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby.  Create scripts in a directory called scripts (in your home folder, like as  ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py :  Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash

Performance Testing on CI: Locust is running on Jenkins

For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients ,   hatch rate,  running locust without web interface and there should be so