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

What will you learn in this lecture?

In this video, we will go through the introduction to single responsibility principle of the page objects in test automation course.

Selenium Tutorial – Page Objects in Test Automation Introduction to Single Responsibility Principle


In this next section I would love to cover with you the Single Responsibility Principle Single Responsibility Principle is another principle that is extremely important for helping you to further make extremely robust functional test automation between page objects the DRY principle and the Single Responsibility Principle. I think that you will probably have a 10000 percent or more increase in the ability of your functional test automation at least I believe that that’s the kind of stability that I experienced from my functional tests. So the Single Responsibility Principle is pretty simple. What it states is that a class should have only a single reason to change the benefits of the Single Responsibility Principle. Is that a change in an unrelated functionality will not break two functionalities or more. What do I mean by that is for example if you have a pizza baking functionality when we change it should not break how the store delivers the pizza. Right. So those two classes should be separate the delivery of the pizza should be independent of the baking of the pizza. And so the change in the baking functionality should not directly affect the delivery functionality right. Not only does it make sense for me code perspective. It even makes sense from a logical world perspective because when a pizza is baked that has no impact on how the pizza gets delivered. And so that’s what the single responsibility is making sure that each class has a single responsibility and a single reason to change so that you’re not breaking other classes. Let’s take a look at a few more examples just so you can better understand what I’m talking about.

Pin It on Pinterest

Share This