AWS Device Farm vs. TestComplete

AWS Device Farm is perfect for small teams who don't have enough resources to conduct large scale testing scenarios or even large teams who would like an easier time with testing on various devices. [AWS] Device Farm makes it very easy to interact with a multitude of devices right from the browser.

Incentivized

Best suited to smaller unit test or tests broken up, couple of forms at a time Not suited - larger regressions test involving multiple systems. - my main regression involving payments has been unsuccessful for the last 3 years despite all working fine separately and while being watched

• 100% compatibility with the installed user base. No simulation, but real results.
• Integration with Jenkins and other CI/CD tools.
• A considerable amount of device types available. Again, real devices in the cloud!

Incentivized

• Identifying UI objects and application structure
• Expandability of tests through scripts and script extensions/plugins
• low barrier of entry (you can get started quickly, and other's don't need much explanation to contribute on a basic level)
• Possibility of Jira integration for reporting
• Relatively few (and usually easy to solve) git conflicts when working simultaneously
• easy handling of test data, also for iterative tests

Incentivized

• To be Frank, I have not found any room where it needs to improve. As whatever we used, It is useful for us

Incentivized

• TestComplete could stand to have a simplified view for different types of users. For instance, as a manager/architecture guy, I'm not so interested in getting into the code and am more interested in file-based interactions.
• TestComplete could use more integration with reporting for things like TeamCity to improve test status visibility.

Incentivized

We have bigger test automation pack using test complete at the same time we also think this is not good performing tool for large number of test automation scripts.

Incentivized

It is usable when you become accustomed to its quirks. Not using it for two months and then you need to re-learn the quirks for some features (but some quirks are so awful that they will never fade from your memory). So, when using it regularly, it is possible to be quite productive, if no big correction in name mapping is needed.

Incentivized

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.

Incentivized

Some bugs were quickly resolved, but most UX quirks of the tool are just marked "as designed". No follow up for enhancement request.

Incentivized

If you develop a mobile application and your testing process goes in cloud, probably you will face a problem - how to implement a stable connection between your mobile devices and testing servers

Incentivized

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.

Incentivized

TestComplete stacks up against them in terms of GUI and seamless performance. It records each and every step and action been performed in the application and produces a detailed report in a well-structured manner. It can connect and access seamlessly among various databases directly to speed up the testing process.

Incentivized

• It impact more and more. Not in terms of ROI but in time as well

Incentivized

• Saves hundreds of man-hours with either QA testing or data entry
• With the small cost of the product, it has saved the company money with both employee costs as well as the cost of mistakes made by human error or software bugs

Incentivized