WebdriverIO VS Cypress

My team uses Vue.js. We use Karma/Mocha/Chai and Sinon and Vue Test Utils to test our Vue components. For E2E testing we use Webdriver.io, but have in the past used Selenium written in Kotlin, and also Cypress.

There were changes to node-fibers that broke at least one thing I used, the sync mode of WebdriverIO. https://github.com/webdriverio/webdriverio/discussions/6702

Ever since WebdriverIO got launched, major companies adopted this tool for automation. It became popular very fast due to its powerful advantages. Since the launch, there have been lots of changes and improvements being made to the tool. In this article, we'll be discussing one of the improvements that have really helped us in writing automation scripts in async mode.

WebdriverIO is asynchronous by nature. Earlier, WebdriverIO used to provide the ability to run commands in sync mode using node-fibers. However, due to some breaking changes in Chromium, WebdriverIO discontinued the support for sync mode. Please refer Sync vs. Async Mode and this issue for more information.

Can you use a breakpoint to see why chromeversion isn't being set? This may be an easier implementation with BS: https://webdriver.io/

-Selenium -Webdriver -Cypress -Puppeteer -Cucumber.js -Nightwatch.js

Selenium, Webdriver

In this article, we are going to see how to automate a web application using WebdriverIO. Leveraging the cross-browser power of Selenoid, by running it on the GitHub Actions and publishing the test results to GitHub pages.

https://webdriver.io/ is a pretty solid option, been using it a few years now and have had no major issues with it.

We wrote E2E tests with Cypress before Playwright was around and it was awful. The API is weird to the extent that it is basically a DSL based on Javascript. And the tests were flaky because rerenderings could happen between Cypress getting the DOM element and interacting with it. It seems they haven't fixed that one to this day.[0]

The team is also very confident about their approach. They build their own asynchronous concepts that are not interoperable with async/await, openly acknowledge that it is hard to wrap a head around and then dismiss these concerns by asserting that "Asynchronous APIs are here to stay in JavaScript.".[1] The Github issue about the lost DOM elements is also full of answers by a team member intent on writing blog posts that explain what the user is doing wrong rather than fixing the root problem.

I'm really glad that Playwright came around. It is intuitive, pragmatic and has none of the problems above.

[0]: https://github.com/cypress-io/cypress/issues/7306

[1]: https://docs.cypress.io/guides/core-concepts/variables-and-a...

It is so easy to start writing tests with Cypress.io. It seems that Cypress opened doors to testing for everyone with basic JavaScript knowledge. However, when the number of tests grows writing new tests becomes harder. And the issue is not just about writing code. Planning new test scenarios, refactoring, configuring pipelines, and getting test run reports. The more people involved in the product development the more visibility the testing process needs.

if you wanna start out with something simple, I recommend you learn cypress test automation. https://cypress.io has all the documentation you could need, and there are plenty of positions open in NL and elsewhere in Western Europe looking for good test automators.

For Cypress component tests, we already should have cy.stub'd the feature flags. The flags work great with a served app, but in a component or unit test, there is no network call to LD; stubbing the hooks is the way to go. Mind that at the time of writing, because of issue 18552 stubbing modules isn't working in the component runner. The same thing is ok in the e2e runner. In the sample repo this will be updated with Cypress 10.

It's one of common complaints about Cypress - instead of having separate cypress init that generates files once, it will just keep creating boilerplate files if you want them or not.

Cypress 9.5: https://github.com/cypress-io/cypress/releases/tag/v9.5.0

Sounds like cypress.io would be a good fit.

playwrite.dev cypress.io katalon.com testim.io

I am planning to do automation using cypress.io I have already started the project and am currently working on it. Is there any proper way to upload projects in Github? We don't upload the whole project file now, do we?

Cypress 9.4 Release Notes