AWS Device Farm vs. Protractor

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

It is a strong fit for end-to-end acceptance and regression testing inside the browser.

Incentivized

• Integration with CI/CD Pipeline
• Diversity in Real Devices over the Cloud
• Pay as you go option
• Reproduce Issues and easily collect all kinds of logs

Incentivized

• Async operations for browser-based validation tests. This kind of feature is a must-have for building tests to scale.

Incentivized

• Interface (CLI) not very easy. Competition has better options.
• Integration with IDE for test case coding.
• Reporting for the test scripts executed.

Incentivized

• It would be great to see the Protractor API implemented successfully inside a non-Angular web application.

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

I got more features and handy within AWS Device farm than AWS Cloud9

Incentivized

Cypress.io is an alternative end-to-end test framework that does NOT use Selenium. Since I've only evaluated this tool as a possible solution, my estimation of its performance against Protractor is incomplete. However, if you and your team are looking for automation solutions outside of the Selenium scope, then Cypress.io may be a good fit given the problems you're trying to solve.

Incentivized

• Quicker testing leads to faster product to market times
• Can deploy updates much more regularly by testing across many devices quickly

Incentivized

• Increased the number of reliable end to end tests inside my test suites.
• Decreased the number and frequency of false-positive test runs/results.

Incentivized