In This Course

Did you know that a recent poll revealed that 80% of QA Automation Engineers cannot run more than 100 functional tests daily, with 95% reliability? Furthermore, over 50% of these Automation Engineers struggle to run between 0 – 50 automated functional tests per day!

Functional test automation is a hard job. However, you can make your job much easier by learning a pattern known as the Page Object Pattern. The Page Object Pattern helps to resolve a lot of the problems that other automation techniques cannot. Making your test automation more stable as a result.

This course is designed to teach you how to properly code the Page Object Pattern using Selenium Webdriver with C#.

However, all of the information here is equally applicable to any other functional testing tool because the Page Object Pattern is a universal principle that makes test automation more robust. Similar to other universal concepts such as Don’t Repeat Yourself or Single Responsibility Principle.

Therefore, if you know Object Oriented programming and a different functional automation tool, you can still comfortably follow along with all of the principles and patterns that I lay out in this course.

In this course, you will learn:

– Why other methods such as Record & Replay or Keyword Driven do not work when it comes to test automation

– What the Page Object Pattern is in automation

– Advantages and disadvantages of the Page Objects

– Amazing tips and tricks on how to:

  • Implement the Page Objects using Selenium Webdriver
  • Improve your Page Objects to follow DRY Principle
  • Improve Page Objects to follow SRP Principle
  • Create amazing Page Objects for gigantic web pages

Free Video Course

In This Lecture

In the previous video, we learned how to add a basepage class to our page objects of the page objects in test automation course. In this video, we will go through a quiz on what about our page objects is WET for the course.

Quiz: What about our page objects is WET?


So let’s focus on following the but don’t repeat yourself principle and to make our page objects less wet.

Over here I mean the visual studio solution and first thing I want to show you guys is that I’ve created an entirely new project called Page object expanded because we’re going to be messing with our page object. And I didn’t want to break what we had before.

So I created an entirely new project copied everything over created a new test called Page objects kind of proceeding as we were moving along just so you can see the progression. And now we can pick up from here everything else is exactly the same. The tests and all the pages and so on and so forth.

The very first thing that I want to bring your attention to is two windows that I have on each side on the left as one page. And on the right is another page. Right. All of our page objects look pretty similar. They have a lot of the same structure in looking at these pages side by side. I would like for you to look and see if you notice any kind of duplications anywhere that the dry principle is being broken. Take a look here. OK. Now I’m going to pull up two more pages one here.

The course this page and then the student dashboard page. Take a look at these pages and see if you notice any kind of repetition. Think about it for a second. When you come back I’ll give you the answer to what here is not dry.

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