Hello all welcome back to the next one. In this lecture, we will actually see a practical implementation of parameters and parallel examples for Selenium WebDriver. So, let me actually bring up Eclipse. And let me bring up the website also. So what we're gonna do here is we're gonna run a login test case, we're gonna come to let's call it.teachable.com, and then click on login. And then we will just log into this website.

And what we're gonna do here is we're gonna log into this website and run this test case in parallely for two browsers, Firefox and Chrome. So basically, we cover those things and we will take input from the test ng g dot XML file, so it will cover our parameters stuff also. Let me minimize it. And let me show you what I have in the eclipse. I created a XML file named it as test in G dash Selenium dash parallel dot XML. What I have here is parallel test suite as the name of the suite.

I provided parallel as test. And thread count is two. So I have two tests here if you guys can see, I have two tests here. The first one I named it as Firefox test. The second one is chrome test. And I'm using parameter to provide the browser.

So parameter name browser is Firefox. And for Chrome, the browser value is Chrome. And then I have one class here. The class name is test Angie underscore Selenium parameters parallel example. I know the name is really big, but it kind of suits it because we are doing the real example with Selenium. We are covering parameters and we are covering parallel both the concepts here and it's an An example of that.

So it's kind of decent name. And it's obviously the same class we're executing here because we want to do the same thing in parallel for different browsers. And here we go, we have our class. So what I have here is the class name, then I defined WebDriver, driver and string base URL here on the top, please make sure to define it on the top. Do not initialize it yet, just define them. And then we will initialize them in the before class method.

And if you don't define it here, you will not be able to use it in other places, like after class in those places. So we don't want to define them inside before class, we want to define them outside and initialize them inside before class. Then we have at the read before class, I initialize the base URL here. And then what I'm gonna do here is I'm gonna make use of the parameters. So add the rate parameters. From test Angie, and inside parenthesis, we'll use curly braces.

And we will say, browser. And this accepts one argument called browser. So it will fetch that browser from the parameter in the test tag, right. Now what we can do here is we can actually use kind of F conditions. So what I'm gonna do here is I'm gonna say if browser dot and equals ignore case. And in this I will say Firefox.

If this is Firefox, then I will do a different setup. Else F. Let me just copy this. So we'll change the name of the browser. And if it's Chrome, then I will do what the setup here. So what I want to do here is if the name of the browser is Firefox, then I will actually initiate the driver as a Firefox driver. And if the name is Chrome, then I will initiate the chrome driver.

So let me just copy the simple line from the small class Firefox driver demo. So I'm copying the system dot set property for Gecko driver and setting up it as a driver as a new Firefox driver. So that's what we are doing. And that's about it. Same thing we'll do for Chrome's I'm going to copy the same thing instead of Gecko driver, I'm going to change it to Chrome driver, and here also chrome driver. So please make sure that you mentioned these locations correctly, right because I know this is my correct location.

And you will have a different location for your project. So name it properly. And here instead of this Firefox driver, we will say, we need a chrome driver. All set, that's what we want to do. This is how we use the parameters. Now we have this setup, I'm going to do a few more things like driver dot manage dot, window dot maximize, and driver dot manage dot timeout, implicitly wait.

And then and I'm gonna provide time unit dot seconds. So we are putting our implicit bear of 10 seconds. And then here I'm gonna use driver dot get and base URL. So that's our setup method. This is all done and said, let me just minimize it. And let's minimize the, the import statements.

So now we have the full focus on at the rate test annotation methods. So I named it as test login and let's see what we want to define here. So let's go to the website. The first thing we want to go here is after reaching the base URL, we want to find the XPath for this login. So I'm just gonna click on this, and it is an anchor tag with the class. I don't want to use this text because I see some whitespace.

So this is a little inconsistent. What I'm going to do here is I'm going to use this as our F attribute. So if HRF attribute contains the sign in text, then I can find it. So let's go back close back again. And I'm gonna say web element. login link equals to driver dot find element by XPath.

And my XPath expression would be a contains inside contains I'll provide accurate HR F comma. And this contains slash, sign underscore in. That's what we did there, right. And after that, put a semicolon. And for web element, let's import it from our dot open QA dot Selenium. Now once I find the element, we will say login, link, dot click.

After the click, we need to find other elements. So let's see what happens when I click on it. So I raced to the new page, and I see other elements as email and password, then I need to find the login button. So these three elements need to find and that's about it for this example. So that's good. This element has an ID called user email so we can simply use it.

So I'm going to define web element and email field is the good name Driver dot find element by.id. And we already copied it. Once we have the email field, we will say send keys and the keys to send his test at the rate gmail.com. I'm just giving any email, so it doesn't have to be correct. Now I'm gonna find the password field. And this one is driver dot find element by.id will provide the ID and then Password field dot send keys and ABC ABC and then finally web element and login button, the one on the down which will enable us to log into our app So driver dot find element.

And let's see what it has. So let's find both the elements together. So for password, also, we have an ID called user password. Let's copy this here. So we're all done with the password field. And now let's figure out the login button.

So input and this one doesn't have an ID, but it has a name called commit. So let's find this element with the name commit. So I think this should, this should be good for us. So by dot name, so we can use pretty much everything here we use by XPath. We use by ID we use by name and it's a good test case. So once we find the login button, what we need to do here is we need to click it and also set so we have our test method done.

We have our setup Already done. And now let's try to run it using the test nj dot XML file. So I'm going to right click this one. And what we expect here is okay, let me know what close this Firefox browser. So we actually don't have anything running. Now we expect Firefox and Chrome to come up in parallel and run the test cases together.

So run as test in G Suite. And let's see. So Firefox came in and chrome came in the both are working on in parallel. As you can see here, this is chrome going on. And chrome looks like it finished a lot earlier. And then at the back now Firefox is going on and everything is done.

So basically, both of them came up in parallel, and executed the scenarios together. And we can see that obviously, there would be some difference. And a little bit of time when chrome came up and Firefox came up depending on our system, Ram speed and memory and also browser speed to sometimes chrome can come up before Firefox and sometimes Firefox can come up for Chrome. But they're still in running in parallel, right? So that's a real example that we wanted to take a look. Please download the code files executed and let me know if you have any questions.

I'll see you in the next lectures guys. Thanks for ending this one. Thanks.