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 the previous video, we learned the description of the 2nd test of the page objects in test automation course. In this video, we are going to understand why page objects look similar for the course.
Page Objects Look Similar
One other thing that’s worth noting about the page objects is that they all are going to look pretty similar. That’s the beauty of this is that because they each represent NHT M-L page they’re obviously going to have some properties and some methods the properties are going to live towards the top or wherever you want to place them and the properties are basically just going to be a bunch of elements. And towards the bottom, you’re just going to have your methods that directly interact with the web page.
Let me show you the coarsest page compared to a different page.
On the left I have the student login page and on the right, I have the courses page you can see how both of the pages have a bunch of elements towards the top and then some methods towards the bottom. All looking similar. And as you go along your way creating your page objects they’re probably going to look similar as well which is completely fine. That’s the nice thing about page objects is that they have a common structure because they’re all representing an actual HTML page.