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 Intro to section regarding dealing with large web pages.
Selenium Tutorial – Intro to section regarding dealing with large web pages
We are about to get into the final section of our quest to drastically improve our page objects. Also tackle all of the most common problems that selenium web driver automation engineers experience as they write their functional tests in this section. We’re going to learn how to create simple page objects from complex web pages. As you progress as an automation engineer you’re going to notice that your classes begin to get very bulky in size.
A lot of times you’re going to get very complicated HDMI and pagers that you need to represent inside of a class. And so they’re going to get really bulky really hard to use and really hard to maintain. It’s a common problem for many automation engineers. So in this section I’m going to teach you how to tackle that problem so that you don’t face all of the issues that result from having gigantic classes.
So some advantages of having simple page objects as opposed to gigantic monolithic dinosaurs is that they are small in code size right. Less code inside of a single class. Easier to maintain easier to understand.
Therefore it’s also easier to manage because everything lives inside of its own small container. Also this methodology that I’m about to show you is going to make our tasks easier to read and easier to write. So all of these benefits are fantastic when we start implementing simpler page objects for complicated web pages.
We are going to need a few resources. Don’t worry it’s nothing complicated. What I’ve done is created in sample automation web page where you can practice functional test automation with different kinds of scenarios.
If you go to that you are l I dare ultimate create slash automation that’s going to get you started on your path to practice the automation page and the automation page or we’re going to use for practice is going to be this ultimate Q8 dot com slash complicated Dasch page.
That is the page we’re going to practice functional test automation on with in regards to the scenario. Let’s go ahead and take a look at those pages right now.