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 fo 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 are going through the introduction to the next section and tools used for the Page Object course.
Selenium Tutorial – Introduction to the next sections and tools used
In this next portion I wanted to take you through a logical progression of automate testing techniques over time.
I wanted to take out through recording replay to keyword driven frame to the page object model.
In each stage, I’m going to help you to understand and identify all of the problems, with that stage and what about that stage makes the automated functional test so brittle.
In the next stage we are going to fix those problems and you are going to see the evolution from one stage to the next.
We are constantly going to be improving, making our automate function test more stable until we get to the final solution, which is going to be out most stable solution, and hopefully you will understand why the evolution happens as it does, and why the stability exists in our final page object model.
Of course I’m going to begin with a little bit of record and replay, here are the tolls that I’m going to be utilising.
Of course, you are not bound to any of these tools, you can do this with any kind of automation tool that you want.
You can do it with any kind of framework that you want, but these are the tools that I’m utilising.
I’m utilising Firefox, Selenium Builder, Visual Studio in c #, of course we can do it in java Binding(?) – it doesn’t matter – I’m using Selenium Webdriver again, all of these techniques apply to any automation tool and any bindings and NUnit is my testing framework.