AWS Device Farm is a mobile application performance testing application that provides real-time automated testing and reproduction of issues, simulating and testing issues that may occur on a variety of platforms (e.g. iPhone or Samsung mobile device, or multiple operations systems, etc).
$0.01
per instance minute
BlazeMeter
Score 8.1 out of 10
N/A
The BlazeMeter Continuous Testing Platform is a unified, end-to-end, next-generation software test automation platform built for both Agile and COE teams, from Perforce. BlazeMeter includes complete continuous testing capabilities deeply integrated into a single, intuitive workflow.
$149
per month
Pricing
AWS Device Farm
BlazeMeter
Editions & Modules
Pay as You Go - Desktop Browsers
$0.005
per instance minute
Pay-As-You-Go
$0.17
per device minute
Private Devices
$200.00
per month
Unlimited Testing
$250.00
per month
Basic
$149.00
per month
Pro
$649.00
per month
Offerings
Pricing Offerings
AWS Device Farm
BlazeMeter
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Device Farm
BlazeMeter
Considered Both Products
AWS Device Farm
Verified User
Anonymous
Chose AWS Device Farm
We haven't used anything like AWS Device Farm before. I am familiar with Amazon Web Services and when we had our MVP ready to test, we turned to AWS for a solution. AWS Device Farm was exactly what we were looking for as we have a really small team and limit resources.
BlazeMeter scores well against Apache JMeter in one Key point , the load generation from different cloud based systems. This helps to measure the capacity of the the application in a transparent way and not bogged down by the capacity of the system from where the test is …
In comparison with Blazemeter the closes competitor is JMeter but it has disadvantages like it is not a tool that can be use as a collaborative tool and works locally in a computer, Blazemeter is in the web so different people can access and run tests or collaborate do add, …
Personally, I prefer using JMeter + Redline13, however we had some business folks that wanted to be able to run a few of their own tests. The non-technical individuals preferred to use Blazemeter because of its simple and intuitive UI.
As long as you have the right scenarios in mind where you can use AWS Device Farm, you will be very happy. It's a cloud platform for testing automation support, where you can use real devices in multiple configs to validate your Android or iOS use cases. It does easily integrate with your CI pipeline, but reporting and UI are not perfect. A pain point is also the JUnit4 implementation, which could be more mature.
It is good for measurements of performance testing. It can be used to run API testing. I can not use this for monitoring but it can be used as a complement for monitoring tools (like Catchpoint or New Relic). It can help to produce load on your site and monitor.
Blazemeter has very intuitive and uncluttered UI. It is very easy for a beginner to figure out and get started.
Blazemeter allows several methods of creating performance tests - using several popular open source applications. Therefore most often there is no need to learn to use a new tool or language.
We had the enterprise support with AWS, so overall support experience was good with great engineers on the back providing answers. As you may know, overall AWS support is different and this is not different. Responses through the regular web support channel came easily, fast and accurate. We had questions/issues which were solved fast. Documentation is good as well, especially around the test automation pieces.
We haven't used anything like AWS Device Farm before. I am familiar with Amazon Web Services and when we had our MVP ready to test, we turned to AWS for a solution. AWS Device Farm was exactly what we were looking for as we have a really small team and limit resources.
BlazeMeter scores well against Apache JMeter in one Key point , the load generation from different cloud based systems. This helps to measure the capacity of the the application in a transparent way and not bogged down by the capacity of the system from where the test is executed (in this case Apache JMeter)