webdriver-bidi VS Selenium WebDriver

fwiw, the Selenium project is now old enough to go to college (19 years this month!); it's not ready to retire just yet. (Side-note: Google Chrome is 15 years old. Age is just a number.) Selenium is still learning from other projects and implementing some new things. Specifically, check out the WebDriver BiDi project, adding a bidirectional protocol which was the core of what made Playwright and Puppeteer faster. Also, Selenium devs are working with the W3C to make this work for everyone.

https://github.com/w3c/webdriver-bidi

https://w3c.github.io/webdriver-bidi/

Is this new WebDriver BiDi available in any of these packages, and does it actually help with this?

If you want to learn more about WebDriver BiDi, you can read the WebDriver BiDi specification.

I guess I didn't understand what exactly you were talking about when talking about "this new standard": WebDriver BiDi or WebContainers.

WebDriver BiDi is on the standards track, that's true: https://w3c.github.io/webdriver-bidi/

One of the new features in the recently released Selenium 4 is support for new event-driven listeners which will be powered by the currently-in-draft BiDirectional (or BiDi) protocol (though the current Selenium implementation has some limitations, which we'll discuss later). In this article we'll discuss some of these new capabilities and demonstrate how to use them in Scala to inspect console logs and network requests made from the browser.

The new BiDirectional WebDriver Protocol is by far one of the most exciting recent developments in the Selenium project and it likely to deliver improvements in speed and stability that far outweigh expectations. As soon as it is available, it will become part of Nightwatch as well. You can follow the development on the Selenium website.

The explainer might be a better starting point: https://github.com/w3c/webdriver-bidi/blob/master/explainer....

There's also the webdriver-bidi spec being worked on by browser vendors that may provide a less hacky, more browser native CDP-style approach to this.

Selenium is an extensively used open-source automation framework for web applications. It allows for cross-browser testing by automating browser actions, making it a staple tool for end-to-end testing in diverse web development environments.

While similar to Puppeteer, Cypress, and Selenium, there are some differences. Let’s find out what they are.

browser.get('http://selenium.dev/')

Cypress is a next-generation front-end Automation testing tool built for modern web applications. It is a JavaScript-based end-to-end testing framework and is known for faster test execution as compared with other testing tools (like Selenium or Protractor).

Removing ExpectedConditions from documentation makes sense since it was removed from the codebase around 2019 already.

https://github.com/SeleniumHQ/selenium --> trunk

You won't be able to test the javascript function itself from within python, but you can exercise the front-end code using something like cypress (https://cypress.io) or the older but still respectable selenium (https://selenium.dev).

once you solve this you may run into: https://github.com/SeleniumHQ/selenium/issues/11750, so add that workaround.

Other libraries with similar functionality are Selenium, which is very popular outside the JavaScript world, and Playwright, a younger step-brother of Puppeteer.

🔗 https://selenium.dev