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 discuss what will be covered in the next section.
Selenium Tutorial – What will be covered in the next section?
In this next portion of the course, I wanted to focus on creating much better page objects. It’s really important to be able to improve upon our page objects because you will notice that although they’re pretty easy to get started with along the way you’re going to come across some challenges that are going to be pretty hard to deal with and you’re going to have many options and you’re going to need to be able to know how to handle all of those challenges. So there are three reasons for this next section.
First is to cement understanding of page objects. Yes I know I gave you a pretty great introduction to page objects but they get much more complicated as time goes by. Therefore with lots of exercises and lots of examples, I really want an all to understand page objects and for you to be able to code page objects in your sleep. Next, I want to improve the code of our page objects. Yes, they are phenomenal and they are way better at helping to make more stable tests.
But then something like keywords and framework or record and replay. However, there are always improvements to be made to the code even to this very day. I’m still learning things every single day that I take into my automated functional tests just to further improve it. And I wanted to show you guys some of those improvements. Finally, I want to tackle solutions to some common challenges. You will notice through your career that as you begin to utilize page objects you will come across some common challenges that we all face as automation engineers.
I wanted to give you some tools to be able to deal with those challenges whenever you come across them so that you are better able to handle them.
So this next section is going to be broken up into three parts. Part one we’re going to make our current page objects more dry as in we’re going to make sure that they follow that don’t repeat yourself principle in the second portion of the section. We’re going to make sure that our current page objects follow SRP. That’s known as the Single Responsibility Principle. I’ll elaborate more on that in a few minutes.
And third we’re going to learn how to use complex pages to write simple page objects because there are going to be times and there are going to be a lot of times when you’re going to have a complicated HVM Al page and so your page object that you use to abstract Dowden HMO page is going to become extremely complicated convoluted and hard to maintain. So you’re going to need to know how to write simple page objects for those complicated HVM pages.