WebdriverIO VS puppeteer

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.

Puppeteer https://pptr.dev

puppeteer-report provides a simple solution for having a custom header, footer, and page numbers. Still, I got a bunch of requests on GitHub for new features and had to reject most of them because puppeteer has a lot of limitations in the customization of layout and printing.

if you can display it, you are likely to be able to scrape it. I would recommend looking into https://github.com/puppeteer/puppeteer . It is a headless chrome implementation for scraping data ( and other things).

You can automate things like this using Puppeteer or Playwright.

If you know a bit of programming, you can use Python and Selenium, or Node.js and puppeteer to automate the task. :)

In a similar vein, I have found success using request interception [1] for some websites where the HTML and API authentication scheme is unstable, but the API responses themselves are stable.

If you can drive the browser using simple operations like keyboard commands, you can get the underlying data reliably by listening for matching 'response' events and handling the data as it comes in.

[1] https://github.com/puppeteer/puppeteer/blob/main/docs/api.md...

You can start a recording, execute the steps you’d like to record in the app (such as typing or clicking), and export the recording as JSON file, Puppeteer script or @puppeteer/replay script.

Well, we have great news. There is a framework called Puppeteer that uses relatively new Chrome feature and makes it accessible though a NodeJS based API.