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 changing the remote webdriver to firefox driver of the page objects in test automation course. In this video, we are going through finally getting the recorded test to run for the course.
Finally Getting the Recorded Test to Run
Now that brings us to our 3 rd class.
C recorded tests with our test 1, we’ve been working at and applying a 2 nd fixing order to get it to run out of the box with a recording.
The recording that supposedly so easy make it run we are applying another fix to it just to be able to get it to run.
So, the fix that I made was I actually am going to stat the driver in maximize state, so that we can always control the size of the browser, so that it always comes up in this state, versus the minimised state that becomes responsive.
Furthermore, I obviously had to update the code, so that now interacts with this link, the SIGN IN link as opposed to this MENU that brings in a dropdown.
So, 2 more fixes that I have to apply in order to get the automated test to run out of the box.
Taking a look at this, do you believe that this test is finally stable enough to run?
Let’s go ahead and see.
I’m going to click here and I’m going to go ahead and run it.
These tests are always really fun to watch them run, I enjoy it.
Finally, we’ve got our recorded automated test to run after 1 enhancement and 3 different fixes,
we’ve got it in a state that we can run it.