Hello everyone, in this video session, I am going to explain part 18 of selenium four that is Selenium web drivers, W three c standardization Selenium WebDriver drivers Wi Fi standardization. So till Selenium three. It will Selenium three we have the normal WebDriver okay. Normal WebDriver API was there in Selenium in Selenium four, okay. In Selenium for that aim is planning to release the W three c standardized WebDriver API. Okay.

So this WebDriver API is going to be in compliance with this w three standards, okay. So there are some w three c means w three stands for W three C stands for World Wide Web Consortium. Okay. So this World Wide Web Consortium has some standards. Till Selenium three, this WebDriver API was not according to the standards. Okay.

This WebDriver API was a normal API. And it's not according to this w three c standards in Selenium for that Selenium team is planning to release the WebDriver API in compliance with this w three standards. Okay, the blue three standards. So this is a major changes, okay. This is a major highlighted change in Selenium four. That is why the standardization of Selenium WebDriver is a wt says standardization of the WebDriver Selenium WebDriver is a major change major highlighted change in Selenium four guys okay.

So, there are other changes also in Selenium four when compared to Selenium three, but this w three standardization of WebDriver API is a major highlighted change in Selenium four when compared to the all the other remaining changes. So, this is a major shift in Selenium for where we are standardizing the Selenium WebDriver according to the WC three w three c standards now Now we understood the major change in Selenium for now let's find out the different advantages purposes or reasons behind the standardization of the WC of Selenium WebDriver. Okay, W three standardization of Selenium WebDriver. Let's find it out. One after the another one. The first one here is WebDriver Our API is not only used in selenium, but also used in other automation tools.

Okay. What does this mean? So, in Selenium tool, there is something known as WebDriver API, right in Selenium WebDriver API is used as part of the Bridgestone Selenium automation tool. But guys, this WebDriver API is not only restricted for using a Selenium automation tool, but also this WebDriver API is used in other popular okay. Other popular automation tools also. There are a lot of tools in the market guys, which are using this WebDriver API of Suriname, okay, they are dependent on this WebDriver API of selenium.

When Selenium team comes up with this server Ever API changes and upgrades, all the other remaining automation tools also will comply with them like they will. They will, like do changes in their automation tools. So based on the changes done in the WebDriver API, okay, they're like they're using this web driver API as a wrapper. Okay. Let me give some examples guys. Let's say there is a tool known as APM tool and I use driver tool, okay, automation tools.

And in this mobile automation market, okay, these tools are targeting the mobile automation market is mobile automation, test automation, tools research. And this appium is driver which falls below certain simple examples, which are heavily dependent on this these tools are heavily dependent on this WebDriver API only Okay, not just the Selenium automation those guys but also other automation tools, like APM, iOS driver, etc, etc. Okay are also dependent On this WebDriver APA So, so, what will happen okay if you standardize the Selenium WebDriver okay how it is going to impact this other automation tools which are heavily dependent on this WebDriver API apart from Selenium automation tool, okay. thing here is standardizing the Selenium WebDriver will result in the implementation of Selenium WebDriver across different software without any conflict compatible issues. Okay. So, these are heavily dependent of WebDriver APA upon upon standardizing the WebDriver API with the W three standards, okay.

As this WebDriver API is used across this other automation tools, okay, the compatibility issues will be reduced that went ahead It is compatibility will improve cross compatibility of Selenium WebDriver will improve and cross under implementing software's, because of this w three c standardization is advantages. Okay. So, upon standardizing this WebDriver API with this w three standards, as this other tools are dependent on this heavily dependent WebDriver API. Okay, they have implemented this WebDriver API as other tools as they're dependent on this WebDriver API has to implement them okay in their tools, automation tools. So, during the implementation, the compatibility issues may arise, a mismatch things may arise. Now, because of this w three standardization, okay?

And all the tools will follow that up. literacy standards. And because of that, because of that, the compatibility issues will reduce. Okay. The compatibility issues will reduce upon implementation of this WebDriver API in other automation tools. Now, it's not just restricted to mobile automation tools like ipmi use case.

There are many other famous core and polis automation tools in the market, which use WebDriver API internally. Okay. So it's not just IBM or iOS, but there are many other good number of famous and cordless automation tools in the market, which use WebDriver AP internally and because of this w three standardization of Selenium WebDriver all these automation tools, okay, maybe mobile automation or other code or codeless automation tools, which are internally implementing WebDriver. Apa will face very less or will improve their compatibility like compatibility between them okay. Compatibility will improve and it shows compatibility issues will reduce because of this stuff. energization Now the next thing Okay, what else we have on standardizing the Selenium WebDriver with the W three standards.

So, this is like the benefit we will we are going to have in Selenium WebDriver itself okay Selenium tool itself that is a till Selenium three okay in Selenium three the things used to be like this here are we have some Selenium three code okay let's say this is some Selenium three code. Okay some code is there here are in your machine or Eclipse ID or something near local mission. And and this is like built on the WebDriver API right. Some API will be there, the Selenium record will have the what will be there in this a code WebDriver API and some programming language will be there. And this WebDriver API in this permission code of selenium three, to communicate with the browsers. On the other end, we have the browser specs.

Okay. Let's say here we have the browsers, different browsers, like Google Chrome, Firefox, ie, etc. Okay, a lot of browsers are there, which are supporting the Selenium WebDriver. Anyhow. So in order to communicate the Selenium three in order to execute the automation code on these browsers, okay, we need to communicate with this browser side Selenium WebDriver. APA, this WebDriver API has to communicate with this browsers for that in Selenium three, a protocol was there.

Okay. protocol is there that is Jason wire protocol. Okay. So in Selenium three, a protocol known as Jason wire protocol was used for communicating this WebDriver API as you wish commands with this on fra tuition under different browsers. Okay. This is what used to happen in Selenium three.

So how it is going to be different in Selenium four in Selenium four because of the W three standardization of WebDriver API, we got a new protocol. Okay. So here again the same here WebDriver API is F for our API let's call it for now. Okay. And in between what is the protocol? We are going to use the protocol he had got replaced JSON via protocol.

What replaced in Selenium four with which protocol? w three c protocol is okay. And on the other side, we have this browsers different browsers like Chrome, Firefox, ie etc Now besides the different browsers we have and wjc protocol used in Selenium for for communicating between this web Selenium for WebDriver API with the different browsers here in place of JSON wire protocol, we are going to use WC protocol as per the standard w three standardization of the WebDriver. API in Selenium four. So is there any difference of using by using this a different protocol here in case of selenium four? thing here is this API requests and responses need to be in case of JSON via protocol of selenium?

Three, this WebDriver API requests and responses need to be encoded and decoded. Okay. Generally we use encoding and decoding for security reasons, okay. So normal text will be replaced by some XYZ text that no hacker cannot understand such kind of things. Okay, technically speaking, okay. So such kind of encoding and decode decoding kind of concept will is used by JSON Web protocol for encoding and decoding the request and response of this WebDriver API in case of selenium three.

But in Selenium four because of this WC three, standardization as per that we are using WCC protocol which doesn't require this encoding and decoding this okay. And direct communication will happen between the WebDriver API browsers here that communication will not happen before the communication happens between this WebDriver and API in this browsers. The requests and responses handled by this JSON Web protocol need to be encoded and decoded but in case of Wi Fi protocol, this encoding and decoding is not required okay. So that is another change is encoding this this actually reduced the efforts okay. So it will be more smooth and the communication will happen more directly than before Okay. Now, the next thing is just because of this drivers w three standardization, okay.

So we are way to get more advantages in Selenium guys, first thing is that Selenium is Selenium WebDriver is going to become standard standard okay. Standardized, okay. Then it's going to become more stable, stable stable as will increase and trustworthy as that communication is going to be improved like direct communication is always going to happen that means it's more trustworthy and it same time guys. Like recall. The software Selenium software delivery is not WAC standardized. That means many companies prefer many companies prefer the automation tools which are WCC standardized so that they can trust them.

Like some tools like UDP or something are rigorously using the market. And some companies blindly trust them because they're kind of standardized, but coming to the Selenium till now it's not standardized guys now in Selenium four is going to be standardized and therefore it's better To be trustworthy and just because of this trustworthiness in the market is going to become more popular in the market okay than before. Selenium is going to become more popular in the market than before because of this standardization of WCC standards okay. So, that is another advantage we are going to get in Selenium for as per this the Selenium WebDriver w three standardization now, and one more thing that has that is going to happen here is till now, okay, till Selenium three. Till Selenium three, we don't have any WebDriver API documentation. Okay.

It is WebDriver documentation, like how each and every command inside this WebDriver API is going to work internally like which method API method is going to be called internally like get method POST method with your your a request and all those stuff are not available. Only the command names and how they are going to work for us to be available. Okay, but in Selenium for asper this router is a standardization process. Okay. So there is going to be okay there is going to be a WCC recommendation document for WebDriver API. Okay working of this WebDriver API.

As per the standardization process in Selenium four, there is going to be, they're going to release a W three say recommended documentation for working of this WebDriver. API S is available at this WAC recommendation document for WebDriver. Up API is now available at this URL base. Let me open this URL. So you can see here this is a Okay, W three see the commanded documentation for this WebDriver API. So Apart from having the commands, we are going even going to have the internals Okay, so, let me show you, let's say let's say these are the navigation commands here, navigate to if you click on that, so in this navigator method we will internally use this POST method, each trip method as post and you are is this is a URL okay that you are going to pass okay to make this work and you are going to pass the URL right there we're going to pass a URL as part of this.

So this is example Yes. Okay. So this is a request body you can say where you are going to pass this you are internally it's going to be like this guys, okay, each and every command in Selenium WebDriver. Okay, we will have an internal request body and all those stuff, okay, HTTP method URL that we are going to pass okay as per the request. Then body where you will mention some application URL and all the stuff okay. Internal internal structure of the APA and everything.

Is now available. Okay as per the recommendations of this w three c recommendations Okay, so they're providing the Selenium guys will know will provide this WebDriver So, W three standardized recommendation document also okay from Selenium four is already on the way they already created to some extent okay. So, there is another change that you are going to see as part of this w three standardization of this Selenium WebDriver where you will see the WebDriver APA, internal working documentation, okay, fine. And just because of having this w three standardization of WebDriver it reduces the compatibility issues that are different supported browsers. Okay. So, like a lot reduces the compatibility issues across different supported browsers, many browsers support the Selenium WebDriver API, right.

So the there is a like a working nature of the browsers is different From each and every browser, right, let's say this is a WebDriver API, let's say. And this WebDriver API is supported on different browsers, like let's say there is something like Chrome browser. Okay. And there is something like Firefox browser. And something like IE browser, Edge browser and other browsers that are different browsers, which actually support this WebDriver API. But the nature of this Chrome browser may be different from the implementation of this Firefox browser.

And it will be different from IE browser. So working nature and it will be different from each browser. Working nature and because of the WebDriver API may have to like work differently with the different browsers earlier. Okay, it is Selenium three, but in Selenium for because of this WebDriver API standardization, okay, so it's going to smooth This process Okay, the compatibility is going to increase like anything, okay? Because all the browser's are going to follow the W three standards. And same time WebDriver API is also going to get a W three standardized.

This makes the compatibility more flexible and good guys, and which actually reduces the compatibility issues across different supported browsers, we are going to see less, we are not going to see compatibility issues when you execute your automation scripts on different browsers. Okay, using the Selenium WebDriver API standardized So guys, this is how wt standardization of Selenium WebDriver is going to impact and give a highlight major change in Selenium four and like that this is going to the major highlight is changing Selenium four just because of all these reasons, guys. So that's it guys. In the next video session, I will explain other pending topics on Selenium 400 new feature space. That's it. See you in the next video session.

Thank you Bye