AWS Device Farm vs. Cypress.io vs. WebdriverIO

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

Everything web-based should be testable. Even our highly dynamic content-providing web application works well. Hopefully, it will get a bigger user base in the future so that one can find even more support at StackOverflow or similar forums.

Incentivized

Best suited where frontend developments are in React and where BDD and TDD test frameworks are to be used. Its syntax is very easy to write and understand. Even the non-programmer can do the initial setup. Not suited when the language you are using is other than Javascript(or Typescript).

Incentivized

• 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

• Cypress automatically waits for DOM elements before interacting dev, this eliminates adding explicits waits in your code.
• Has built-in recording and debugging tool.
• Cypress has executions faster since you can update your code in the fly.
• Very easy to configure / setup

Incentivized

• numerous integrations to tools
• fast easy location of page elements
• tool setup is amazing - they have a script to walk you through everything with prompts!!

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

• There are a lot of plugins but several of them have many errors. So Cypress.io should work integrating more features so that people should not rely on these plugins. For example, many people use cypress-cucumber-preprocessor and Cypress.io can start by integrating Gherkin support by default so that reliance in plugins are decreased.

Incentivized

• wdio.conf can contain too much where everything is encapsulated there, like the before and after functions
• A data provider-like testing would be useful. The only way to input different data into the same test is via a loop
• everything is needed to be done using the 'browser' object. Can be limiting where you don't have access to the browser depending on where you are in the code

Incentivized

Highly satisfied and [a] big fan.

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

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

Execution speed and interactive debugging tool is very easy. you can make changes in the fly and test will run automatically, thus saving more time debugging your code. Can easily be intergrated to to CI/CD pipeline

Incentivized

Other tools we selected don't work in our application, it does or doesn't support multiple frames or need more tweaking just to make it works. When testing out WebdriverIO it just works as expected, no need to do such walk around to make it works multiple frames. It also can handle multiple tabs and windows.

Incentivized

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

Incentivized

• Flaky tests can be caught easily
• Regration testing of application with Cypress.io helps to maintain quality of the software product.

Incentivized

• It helped in cross browser testing
• It helped in automating multiple browsers at a time.
• Code coverage is optimum as this supports Javascript(Typescript)

Incentivized