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 Course Reveals Page Objects in Test Automation”]
What will you learn in this lecture?
In the previous video, we learned the introduction to the page object pattern of the page objects in the test automation course. In this video, we will go through the Executing the solution to the quiz of the course.
Executing the solution to the quiz
Let me run the test to show you that it passes.
Fantastic it passed. Now let me read around this test to show you that it fails I actually think that’s even more important than making sure that test passes. So I placed a breakpoint here and those cert and I’m going to debug. Up until this break point and then what I’m going to do is manually close the toggle so that it actually is close and then we’re going to check the assertion to make sure that it fails if the toggle is closed. So I’m going to come back here and I’m going to close this toggle so is closed. Go back to the code and let me step through this. I’m going to utilize the explicit way again. We’re going to check to see if the element is visible which is not going to be visible so it’s going to wait for five seconds and then throw a webdriver time out exception. See that through a web drive or timeout exception going to return false. And then of course our assertion is going to fail and so will our test. It will fail correctly which is expected behavior which is awesome. So again I hope that you got the answer if not no big deal. The important thing is that you get in deliberate practice to maintain all of this knowledge.
[Tweet “Free #Selenium Course Reveals Page Objects in Test Automation”]