https://www.techtarget.com/searchcloudcomputing/tip/Compare-web-and-mobile-testing-tools-from-AWS-Microsoft-and-Google
The hardest part of getting started with web and mobile testing in the cloud is picking a tool that works for testers and developers -- one that is both intuitive and easy to set up.
In the public cloud, you can virtually access a large variety of mobile devices and browsers for test and dev. For a fee, you'll get device access without having to manage, secure or house your own test lab.
And while there are numerous web and mobile testing tools available from a range of vendors, we'll stick to the services offered by the three major public cloud providers for the purposes of this piece. Let's review and compare the capabilities available on AWS Device Farm, Google Firebase Test Lab and Microsoft Visual Studio App Center Test to see which best meets your testing needs.
AWS Device Farm provides accessible testing across a variety of established browsers and mobile devices. AWS handles provisioning and management of all devices, so users can focus on test structure and execution. AWS Device Farm includes these features:
AWS Device Farm pricing starts at $0.17 per device minute for mobile testing, though users can start with 1,000 free minutes. Unlimited testing starts at $250 per month, and private device farm access starts at $200 per month.
Google Firebase Test Lab is another popular option for mobile testing in the cloud. Similar to AWS Device Farm, Google Firebase Test Lab offers testing with a variety of real mobile devices for iOS and Android. Its functionality is similar to testing on an actual device. Test Lab features include:
Google Firebase Test Lab offers a free version that includes 10 virtual device tests and five physical device tests a day. The paid version -- the Blaze Plan -- is pay as you go and charges $1 per device per hour for virtual device tests and $5 per device per hour for physical device tests. Google Firebase Test Lab only works with mobile devices and there's no option for testing with different browsers on nonmobile devices.
One significant reason is your customer base. Do you know exactly what version and platform they use for mobile and the web? Do you know if they are still using Internet Explorer 9.0, for example? Whatever browser they use, your web application is expected to function flawlessly. The same is true for mobile devices. Many users stay with the phone they know and understand and expect mobile apps to function flawlessly regardless of device age or screen size.
Additionally, the number of dependencies on remote services and interconnected apps is steadily increasing, so an application needs to work on as many devices, platforms and version combinations as possible.
Don't count out Microsoft Visual Studio, which offers App Center Test -- or Test Cloud -- for mobile testing in the cloud. This service features:
If you already have Visual Studio, you can use the free tier, which includes 240 build minutes every month. There's a 30-day free trial available for unlimited testing on a single device. After the free trial, App Center Test costs $99 per month per test device concurrency. Similar to Google's Test Lab, Microsoft's App Center Test only supports mobile devices, with no browser testing offered.
In my experience, developers are impressed with AWS Device Farm, even though it's often too expensive for extensive QA testing. Many users find it easy to use and access. Google developers prefer Test Lab for the same reasons.
Microsoft's Visual Studio App Center Test is a complex, interwoven option with endless possibilities if you can arrange it optimally. Developers and testers who are already familiar with Visual Studio will find it easier to use than open source tool sets. However, unless all your applications are mobile, it's difficult to justify the cost of Test Lab and App Center Test due to the lack of browser support.
The best way to sort through these mobile testing tools is to create a test suite that you can execute within the free trial period for each tool. That way, you can compare the test execution, results, storage and automated tool integration across the board using the same exact test suite. Assemble a small set of testers unfamiliar with a tool and determine how easy it'll be to use for your team.
And of course, consider the cost. Determine the amount of testing you can afford. Use the tool for your most critical tests and, ultimately, decide which platform option would be the best bargain for you and your application's quality.
21 Feb 2020