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 identifying what can we do to fix the problems with recorded functional test of the page objects in test automation course.
Selenium Tutorial – Page Objects in Test Automation What can we do to fix the problems with recorded functional test
Looking at this record a test in front of you and just all of the lines of code and the constant duplication. I bet you already know the solution. I know. I bet you know that all you have to do is take the duplicated lines of code and stick them inside of Method. If you place them inside of methods they will allow us to reuse our code over and over again. So if you wanted to type in a username with these three lines of code rather than copying and pasting them from test to test now we’d just place them inside of a method. If you wanted to type in a password rather than constantly copying and pasting these three lines of code we just place them inside of a method and obviously that’s the purpose of methods. They allow us to reuse our code and decrease maintenance because when something changes like a locator for that method all we have to do is go to a single place and updated there. And now all of our tests are going to be easily updated with all that said and then knowing that you need to replace everything with methods that kind of brings us to our next level of automated functional testing. And that’s known as keyword driven testing basically keyword driven testing is utilizing a bunch of methods also known as keywords that we call in a specific order to perform a bunch of actions. Let me cover that more in the next section.