WebDriver BiDi Protocol | Codoid смотреть онлайн

#selenium4 #seleniumwebdriver #WebDriverBiDiProtocol

As a leading QA company, we are always focused on the new automation tools and the new features they bring to the table. In this video, we have explored WebDriver BiDi (Bi-directional) Protocol in Selenium 4. The need for the BiDi Protocol that will establish bi-directional communication between the server and client arises when the client wants to track the Java Script errors that happen in a webpage. Though you can use the HTTP protocol for this purpose, it is not an optimal choice as the Selenium WebDriver has around 60 endpoints to communicate with a remote server. So if there is a webpage that has 100 console log messages, then the server would have to establish 100 HTTP connections. Moreover, we know for a fact that the Selenium WebDriver Remote server does not send any HTTP response or message to the client until it receives an HTTP request. But using the WebDriver BiDi Protocol, the client will be able to receive all the JavaScript errors by just subscribing to it once. It gets even better as you can stop it in one step as well. Want to know more? Watch our video.

0:00 Intro
0:20 Why do we need WebDriver BiDi Protocol?
1:42 Why does Selenium 4 use the WebDriver Bidirectional protocol?
3:02 A WebSocket Example
4:58 Sample Code to understand WebDriver BiDi Protocol

If you want to view the code shown in the video, you can visit our website and read our blog about the very same topic from this link - https://codoid.com/an-introductory-guide-to-the-webdriver-bidi-protocol/