Cypress.io vs. Protractor vs. WebdriverIO

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

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

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

• 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

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

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

• 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

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

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

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

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

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

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

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

• 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