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 are going through understanding why the test failed a second time for the Page Object course.

Selenium Tutorial – Understanding why the test failed a second time

If you were paying attention, I accidentally made a mistake.

I didn’t mean to make this mistake, but it’s a fantastic one because it’s a fantastic example of all the things that can go wrong with record and replay along the way

What I did was, instead of opening the window in full screen, as it is here, what happened was, I actually opened it in a view like this.

Remember? So that I was on the right side?

And then I had the (inaudible 00:37) on the left side.

So, when that happened my application is responsive and so instead of having a signing link here, it actually becomes a menu, and so it requires us to click on the menu, and then click sign in.

But when Selenium web driver pulls up Firefox, it pulls it off for almost full-screen mode, and so, therefore, the menu and the dropdown is not visible and therefore we cannot interact with it, and so these lines thereof interacting with the tag, and the clicking the sign in link don’t exist anymore because web driver does not open in the appropriate size, and so – again – our test is broken, and we have to apply yet another fix to the recorded test before we can even start running it regularly.

Pin It on Pinterest

Shares
Share This