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 on Executing the solution to the quiz.
Selenium Tutorial – Executing the solution to the quiz
Let me run the test to show you that it passes.
Fantastic it passed. Now let me read around this test to show you that it fails I actually think that’s even more important than making sure that test passes. So I placed a breakpoint here and those cert and I’m going to debug.
Up until this break point and then what I’m going to do is manually close the toggle so that it actually is close and then we’re going to check the assertion to make sure that it fails if the toggle is closed. So I’m going to come back here and I’m going to close this toggle so is closed.
Go back to the code and let me step through this. I’m going to utilize the explicit way again. We’re going to check to see if the element is visible which is not going to be visible so it’s going to wait for five seconds and then throw a web driver time out exception.
See that through a web drive or timeout exception going to return false. And Dan of course our assertion is going to fail and so will our test. It will fail correctly which is expected behavior which is awesome.
So again I hope that you got the answer if not no big deal. The important thing is that you get in deliberate practice to maintain all of this knowledge.