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 this video, we will go through on Cleaning up large page objects example 2.

Selenium Tutorial – Cleaning up large page objects example 2


So running this test while it’s running remember that the vantage Here now is we have very nice and small classes that are much easier to manage than a giant monolithic class that would have been had we continued to automate this page fantastic.

This test has passed.

Let’s go ahead and automate another one clean up.

The other one so here Ian. Test for. We’re doing the search feature. So the search feature that we’re doing is I believe we’re using this search button in the left section.

For our purposes I’m going to call this the left sidebar the right side bar and the center center content. Again let me called this out and you just follow along. Now complaining about the search which of course doesn’t exist in the class.

So we’re going to take the search put it in our newly created class let’s make sure there are no more errors no more errors. Fantastic let me do one more thing and move these to their own files. Look how tiny and small This class is. Further in enforcing the Single Responsibility Principle.

Really great. This one as well. Let’s move it to its own class. Save all of that. Take a look at our test again. Look at that complicated page that left side bar dot search and handed searches.

And then we just asserted that the complicated pages there.

So the test is even more readable. Wouldn’t you agree that you can do complicated page dot and now you have access to these properties here and then through these properties you can access more methods.

And also if we did not utilize this method what would happen is our ID here would get so packed with different types of methods and whatever other properties we were utilizing here and so it would get very bulky and annoying to navigate through it.

So this helps with that as well as always let’s go ahead and execute our test.

Fantastic test for we’re successful and that is awesome.

Pin It on Pinterest

Share This