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 explaining the possible problems that we will run of the page objects in test automation course. In this video, we will go through the Page objects look similar of the course.
Page objects look similar
One other thing that’s worth noting about the page objects is that they all are going to look pretty similar. That’s the beauty of this is that because they each represent HTML page they’re obviously going to have some properties and some methods the properties are going to live towards the top or wherever you want to place them and the properties are basically just going to be a bunch of elements. And towards the bottom you’re just going to have your methods that directly interact with the web page.
Let me show you the coarsest page compared to a different page.
On the left I have the student log in page and on the right I have the courses page you can see how both of the pages have a bunch of elements towards the top and then some methods towards the bottom. All looking similar. And as you go along your way creating your page objects they’re probably going to look similar as well which is completely fine. That’s the nice thing about page objects is that they have a common structure because they’re all representing an actual HCM page.