AWS Device Farm vs Digital.ai Continuous Testing comparison

"What I like best about AWS Device Farm is that it offers actual physical devices that let you do more accurate testing because physical devices depict the live testing scenarios much better as opposed to emulated devices. AWS Device Farm is a pretty nice solution. Because it's an AWS service, you can use the CLI to tie in several steps that can create the pipeline, and run it efficiently. AWS Device Farm also gives you monitoring ability, observability, logging, etc., so I'm pretty satisfied with the solution."

"I rate the stability an eight out of ten."

"Experitest is one of the only companies to offer a real device on the cloud to perform testing. They also provide quality documentations that help you navigate and maximize the solution."

"The most valuable part of Experitest is the number of real devices on which the test is run."

"The most useful feature for me is Mobile Studio. It has a UI where I can click on elements, and it generates a script for me. Mobile Studio can generate code from testing steps. I'm using Python with it."

"An area for improvement in AWS Device Farm is that it lacks a lot of features that would tie it in with other AWS services. The solution doesn't have great connectivity with other services offered by AWS, for example, AWS Secrets Manager. This should be improved because a lot of times, that missing functionality hampers the quality and engineering standards in terms of deploying the full AWS suite of services. What I'd like to see in the next version of AWS Device Farm is for it to link better, or have some type of enrollment that would tie it in with other AWS services, such as EventBridge, Lambda, Secrets Manager, and any other new service from AWS."

"It is slow. It is super slow. Performance is an area that can be improved."

"I have been automating tests for many years on many things but not on mobile devices. The amount of time that I have spent on just figuring out how to use Experitest and get it to work was quite long compared to what I have been doing before. I spent the first two weeks just getting it started. It would be good to have some video explanation of how to use it on your devices and get started. Their online documentation is quite good and extensive, but it would be quite good to have some end-to-end examples demonstrated."

"The integration process was good, but I've faced some challenges. Every time they release a new version, I find bugs in the UI and features. Sometimes, buttons don't work well. When this happens, I submit a ticket to technical support, but they often have to fix it in the next version."

"I would also like to see more videos and descriptions that could make installation more efficient."

"AWS Device Farm is an expensive service overall. You pay per device, and the cost for each device isn't cheap. My company paid for a device slot. It's a yearly subscription for a single device slot, so that's more cost-effective for my company. On a scale of one to five, where one is very expensive and five is very cheap, I'd give AWS Device Farm a two. It's on the more expensive side."

"We make monthly payments. The cost is dependent on the number of devices we intend to support."

"It is quite fairly priced, but it really depends on your budget. It is somewhere in the mid-range of products. It is not free and it is not QGP that nearly costs a whole house. You pay for the number of users who require access to execute the tests."

"The price is reasonable for our company, but I'm not the decision-maker."