AWS Device Farm vs OpenText UFT Digital Lab 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."

"The most valuable feature of this solution is virtualization."

"There are numerous valuable features such as automation, the ones that facilitate importing and synchronization capabilities between our platform, Jira, and Azure DevOps."

"For automation testing, the tool provides the record and playback option, which helps with object detection easily."

"The product is easy to use."

"The fact that it allows users to test on real mobile devices instead of emulators is something that projects have told us is beyond compare."

"It is a complete solution for mobile application testing."

"The solution is easy to use. There are features to orchestrate mobile testing, including mobile testing automation. You can test different devices at the same time."

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

"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."

"The product's object detection method needs to be improved since it can help testers do perfect testing."

"For the most part, the key challenge is ensuring that customers fully utilize the product as intended and adopt the appropriate frameworks to implement the solutions effectively."

"The documentation and user interface both need improvement."

"We like to host the tools centrally. We would need them to be multi-tenants, so different projects could log on and have their own set of devices and their own set of apps, and they wouldn't see data from other projects that are using it."

"We need to scale devices easily. Some customers would like to loop in AWS or other cloud providers to check if their devices have the cloud factor. OpenText UFT Digital Lab needs to improve it."

"They should introduce a pay-per-use subscription model."

"I would like to see more integration with automation tools."

"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."

"OpenText UFT Digital Lab's pricing is average, and I rate it a five out of ten."

"The product could be more affordable."

"While the pricing may seem relatively high, when compared to competitors, it often falls in line or can even be more cost-effective."