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 Disadvantage of an implicit wait 2 of the Implicit and Explicit Waits course.
Selenium Tutorial – Implicit and Explicit Waits Disadvantage of an implicit wait 2
The other disadvantage with implicit Waits is a condition that I’ve seen all too often. We sometimes as automation engineers want to make sure that an element does not appear on a page before proceeding. For example if I come over to our famous dynamic loading page and I click the Start button look at this loading icon. Has it not been so common that a lot of us will wait for this loading icon before proceeding. Imagine that rather than checking for this hello world text this page is not static that this loading icon is used to represent the loading of our page between different kinds of pages. So for example if I’m navigating to this page there is a loading icon now. If I’m navigating to this page now there’s a loading icon present rather than looking at this thing up here spinning. I am seeing a loading icon here. Imagine that imagine that I’m clicking this stuff and seeing a loading icon. Now we wouldn’t be able to know what’s coming up on the next page. Or rather we would need to wait until the loading icon has disappeared before we proceed with our next action. That happens a lot. And I’ve used that technique many times at my job. And so when we want to make sure that an element is not present on a page our implicit weight is going to wait for the duration of the time until that element has expired and the has thrown a no such element exception.
So if we have said this to 30 seconds for our page now we’re going to be wasting in sitting for 30 seconds waiting for the bar to not be present before catching the exception and then proceeding with the rest of our actions. And that is obviously a huge waste of time because we don’t need to wait for that long. We just need for the element to disappear and once it’s disappeared we can proceed. But that’s not how a find element works right. You’re going to find your element which is the bar and then it’s going to wait for 30 seconds and then when the time when no such element exception is thrown we’re going to catch it and then proceed with the rest of our actions. So I hope that both of those disadvantages are very clear to you and implicit. Wait it is great to start helping you write your tests and make them stable and make them Ron. But it’s going to be very inefficient when you have thousands of tests running and you’re going to be wasting valuable valuable seconds that you cannot waste when you have thousands of tests that are automated or even hundreds of tests and so therefore any driver provides us a much better solution than the implicit weight. And that is known as an explicit weight and the explicit weight I’m going to cover further in the next lecture.