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
In This Lecture
In this video, we will go through the answer on the quiz on what about our page objects are WET.
Selenium Tutorial – Quiz answer to why our page objects are WET?
The problem with Page objects and why are where it is that we have constant constructors being repeated over and over only the name of the page changes. But what we’re doing in the constructors is always the same we’re always setting it to a driver.
So, therefore, that’s redundant and doesn’t have much purpose and obviously going to causes problems whenever we need to maintain stuff. The solution to that problem is to add a base page class that will help us to control a lot of our common elements throughout our pages.
I’m going to quickly code and add the base page here and then we can talk about what I did after.
All right. So the base page has been added. Let’s go ahead and walk through what I just did. And the purpose of it.