What will you learn in this course?

Are you struggling with working with HTML using Selenium WebDriver? Do you know how to easily identify and manipulate an element using Selenium WebDriver? How about performing a drag n’ drop on an element? If not, then these are just a few of the questions that will be answered in this course.

This course is a complete guide on working with web elements in Selenium WebDriver! Once you are finished with this course, you will know how to work with any web elements, anytime, on any web application.

In this course from Ultimate QA, you will learn:

– Basics of HTML

– All the different locator strategies for Selenium WebDriver

– How to identify web elements using Selenium WebDriver

– Master XPath

– Navigation with Selenium WebDriver

– Web element manipulation

– Web element interrogation

– Mouse and keyboard actions with Selenium WebDriver

– Performing actions such as drag n’ drop, drawing, hovering

– Implicit and Explicit waits

– How to properly handle element identification so that your tests are not flaky

– Expected Conditions in Selenium WebDriver

Take This Entire Course for Free

[Tweet “Free #Selenium Webdriver tutorial reveals how to execute parallel testing in Sauce Labs and Browser Stack”]

What will you learn in this lecture?

In this video, we will go through the How to execute parallel tests in browserstack of the Fast Tests Execution course.

Selenium Tutorial – Fast Tests Execution How to execute parallel tests in browserstack

So quickly just to summarize exactly what I did. So now we have three browsers stacked us right test Twan runs on safari and OSX test who is going to run on Windows 10 on Firefox and Turse 3 is going to run on Android Galaxy S5. OK. So three different times do kind of three different things. We just need it to our data capabilities. They are all parallelize the bowl right which is going to allow us to run them in parallel. And now let’s take a look at the Tests to Explore the tests aren’t there. We only see our first one right of course and that reminds me. Let me update the test names so we go in here to see test too. And let me go to test three. I did this to test all three. Awesome. So now you don’t see these tests right. Why not. Can anyone answer of course is because we didn’t build yet. So I’m quickly going to build these projects. Give it a second build succeeded. Now if you go to the test explore you’ll see two run tests because we just created them. The other one we ran before. So what I’m going to do is run all three of these tests in browsers stack. So let’s me do run select the tests and then I’m going to pull a browser stack and show you guys exactly what is going on. Check it out. Run select the test started. Here comes the browser stack. Let me scroll up. Go to automate tab and bow right here. Check it out.

Three tests running in parallel Safari Galaxy S5 and Firefox windows 10:43. So here are the test running. Check it out. Once finished and you can see it’s recorded a video visual logs I can’t see because debug is not so true. True but we can see the video. Here it comes. Boom pulled up. That’s Sheean Snow Leopard on OSX. What happened here. Here it worked ok. Couldn’t find the bun that it wanted but that’s fine. And now Galaxy S5. Let’s see what is going on here. Still running their goals pulled up our mobile device. Check it out. We can make this a huge session. You can make it in Iraq of session if you want to. That’s really cool. So all the testers running you can click in interactive session you can go in here and you can actually screw with the test while it’s running. You know if you want to open another window and see it break you can if you want to like pause it and do something now make the test break you just go inside of there and break it. It’s really cool. You can put like a breakpoint open up and you Taieb and then see if your test will actually fail. So anyways that was three browsers stack us running in parallel and you guys can see how awesome that was right they only ran as long as the slowest test. And in this case those are Galaxy five-Test that took a few minutes to run which you can actually see how long they took to Ron. It took a minute 28 seconds to run.

So that’s another great thing right. You see they time everything for you get everything out of the box. We didn’t have to do anything. We just literally wrote a test and you get all of these features out of the box from these cloud services. That’s why I love them so much more than using something like Millennium grid because I personally could never dream of having a framework this amazing without the services.

[Tweet “Free #Selenium Webdriver tutorial reveals how to execute parallel testing in Sauce Labs and Browser Stack”]