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 the previous video, we learned advantages and disadvantages of the page object pattern of the page objects in test automation course. In this video, we will go through the explaining the possible problems that we will run of the course.
Explaining the possible problems that we will run
Now that we’ve written a few tests three tests for the complicated page and we’ve done some deliberate practice with everything. Let’s take a look at the complicated page to see the problems that we’re going to run into and how to resolve those problems. So if we take a look at the complicated page now you can see that it’s beginning to get a little bulky right now. It’s definitely not so bad but we have only written three tests and it’s already about 60 lines of code and you can see that if we continue to work with this giant complicated page we’re going to run into a problem where our class is gigantic and harder to maintain because it’s so gigantic there’s going to be so many things and you need to keep track of so many variables and methods and so on so forth that your idea each is going to become very bulky.
So in order to improve that we can actually start rapping a little sections of this page into their own classes. That’s completely ok because it’s going to make each of our classes smaller. And then it’s actually going to make it even easier to interact with our IEEE into write automated functional tests. So for example the way I would look at this page and logically break it out into sections is I would probably break it into a section called section of Baden’s where I just interact with the buttons a section of social media follows where I just interact with the social media follows and then even a section of random stuff is actually itself pretty big.
So I might break it up into more sections than that so I might write a class that’s called section of random stuff and then that section of random stuff might contain a class that’s called the left side bar the right side bar and then I don’t know what we call the center the center. Posts the center section. Yeah the center section. So we could break it up like that. So actually let’s go through the code and let me show you what I’m going to do and I’m again I’m going to implement one real time and then I’ll explain you what I did and then we’ll implement another one again after you understand what I did.