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

What will you learn in this lecture?

In the previous video, we learned how many functional tests can you run per day of the page objects in test automation course. In this video, we will go through on how can we handle automation in an evolving world of page objects in test automation course.

How can we handle automation in an evolving world

Why is functional test automation so flaky. What is it about it that makes automated software testing so hard. Well I believe that it all comes down to the evolution of the web. Over here what I’ve done is captured an image from evolution of the web that that represents all the different technologies of the web over time.

On the left hand side it started about the 1990s all the way to the right hand side where you can see it’s about 2012 2013 and if you carefully look at the same age you can see that there is a different proliferation of different kinds of technologies. But not only a proliferation but also an increased integration between the different technologies. That’s why you see less colors on the left. And as we merge more to the right there is a more of a mass of all of these colors. And so the reason for the evolution of the web is because of the and user experience right. Everybody who’s designing web applications nowadays wants the end user to have an amazing user experience. And so all of these technologies come along that help the end user to have an amazing user experience technology such as Rigi and canvas starts to come along. We start developing things such as drag and drop and touch events. Think about it in the 90s there were no tablets. There were no smartphones. There were no touch screens and now there are touch events and drag and drop events to be able to handle those different kinds of functionalities.

We’ve created things such as Ajax so that we can asynchronously be loading different parts of an application while one part of the page has already been loaded even angular J s that allows us to execute a bunch of javascript files to be able to more seamlessly run the application so that one part of the page can do one thing and another part of the page can do another thing and in one event can trigger another event and so on and so forth. And this is all phenomenal. All amazing progress for the web but it socks for as automation engineers because we are the ones that have to automate against this constant evolution of technologies. And so that’s why it is extremely hard and functional tests are deemed this flaky because we have to be challenged with all of these different technologies. So how can you handle such an evolving world. Right. When everything when the web is changing so fast with so many technologies how can we keep up the able to do good functional test automation. Well in my personal opinion I believe that it all comes down to a mindset change and you need to understand that the only thing constant in software development is change. If you can understand this concept and believe that change is inevitably coming then from this point forward anytime you make any kind of update to your functional test you will need to keep in mind that your functional test is going to experience change and so you need to be able to insulate it against the change that is inevitably coming. And I wish I could remember where I got this quote I probably read it in a book written by some actually smart individual and it stuck with me ever since because I understood that yes this is true. And once I got that point from that point forward I began to take actions to insulate my automated functional tests from any kind of changes that are going to occur in my application other tests.

Nikolay Advolodkin is a self-driven SDET on a lifelong mission to create profound change in the IT world and ultimately leave a legacy for his loved ones, community, and the world at large. Today, he serves as the CEO and Test Automation Instructor at and contributes informative articles to leading test automaton websites like and

Pin It on Pinterest

Share This