WebdriverIO Vs Selenium Webdriver (Java approach)

Question

Any feedback on WebdriverIO vs Selenium with Java? I am in a dilemma and wanted to clear up this confusion.

I spent several days studying WebdriverIO, and also took some practical steps, but came to the conclusion that it is not mature enough. Debugging is really a problem.

Answer 1

WebdriverIO is an implementation of the JavaScript / nodejs API (Selenium 2.0) WebDriver is one of many (Selendroid, protractor, etc.). The specification says:

WebDriver is a remote management interface that allows introspection and management of user agents. It provides a neutral platform and a wired protocol language as a way for extracurricular programs to remotely instruct web browser behavior.

If you use Java, you will use the Java WebDriver implementation . Which language and which implementation you choose depends on you, your skills and the skills of your team.

Although I highly doubt that WebdriverIO is not mature enough. WebDriver is a great specification with many powerful implementations, but it is very often used incorrectly. Of course, as beginners begin, a very large proportion of "random" failures completely exclude race conditions in their test code.

Answer 2

So, we use the Java test environment - Selenium, Serenity, JBehave, and then Javascript WebdriverIO, Mocha and Yodda.

I think the Java approach is easier to understand and debug. It’s easier to understand, because website testing is basically consistent, you move from one page to another, click a button and fill out the form. This will save you from any asynchronous access problems that you use using an alternative to JS. Debugging is very nice because you have classes and a fixed structure to everything.

The second project uses NodeJS in the backend, so integrating the testing framework was much easier. The testing framework has become part of the deployment / development process.