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 answer why does our test fail when it runs of the Implicit and Explicit Waits course.
Selenium Tutorial – Implicit and Explicit Waits Answer Why does our test fail when it runs
So let’s see how you guys did and why did this test actually fail. If you pay close attention to the page you’re on the right. What I’m gonna do is I’m going to hit the start button and you guys see this loading screen right. And then after the loading screen comes up the hello world. Now if you take a look at the code we navigate to the. We hit the start button and then we check to see if hello world is present. And that is where our actual problem is that little quiz was kind of a prelude to the idea of synchronization which I just wanted you guys to think about before we actually dive into it. The idea of synchronisation is that you want your test running at the same speed as the actual application under test. You don’t want it to be running too fast and you don’t want it to be running too slow because both of those situations lead to negative outcomes from your tests. And so in our case the test was moving too fast for the application right. We were navigating or URL We were clicking the start button and then we were looking for an element that was not there because the loading bar was loading. And so we’re trying to find the element that didn’t find the element and then it said no element there sorry. Let me throw an exception. And so that is exactly what happened. Let me show you guys from the actual age here.
So if you look over here they are male and we look in here we can see that there is a Hello World present in the age to male but its style is display non. So it’s not being displayed. OK obviously until this loading bar has finished going at that point. Now if we hover over it and click hit hello world does not have a style of displaying non-A anymore. Instead the start and the loading icons are now displaying non-right because they are no longer here displayed on the page. And so they’re hidden and they can’t in being interacted with. But the hello world can now be interacted with. And so again that’s the whole reason why our test failed. Because when I was stepping through it I was slow enough for the application to catch up to our test. But when I ran it in the actual continuous integration environment and by continuous integration I mean just running it on my computer. The test failed because it was too fast.