Protractor vs. WebdriverIO

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

• 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

• 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

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

• 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