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
What will you learn in this lecture?
In this video, we will go through the process of setting up another local test of the Fast Tests Execution course.
Selenium Tutorial – Fast Tests Execution – Setting up another local test
OK. So let’s quickly write another test over here. We’re going to do a public avoid local test 0 2. I’m going to do same thing driver and navigator go to your Array. And then you are going to assert is False False just a little bit of a different test and obviously throwing the test attribute there so that our visual studio knows it’s a test and we know how to run it.
Now let’s take a look at our test Explorer here. It only sees one test. That’s because you have to build first. So I’m going to use fix to build and you use whatever keyboard shortcuts it is for you to build. And now that I’ve built I’m going to go up here to the test explore and I can see two Turse one ran and past and one was not run. So I am going to run both of them so I can do that by doing the run all. And so we’ll see what’s going to happen. So you can see it’s setting up here loading tests now running the tests here pulled up the first test and now it should pull up a second test then run that check it out.
Here’s the second test. You guys see that it pulled two tests but did you also see what happened in regards to how the tests were executed. First it executed one test then it executed another test. Therefore that’s where parallel testing comes in handy is because you can run your tests in parallel and not sequentially.
Therefore you can see the more tests that I was adding the longer and longer that time of run is going to take. And in fact it would basically double in this case because the tests are exactly the same. So let’s fix that by setting up a parallel test. We’re going to run locally.