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 are going through the introduction and question for the Page Object course.
Selenium Tutorial – Introduction and question
Welcome to a Single Pattern to Drastically Improve Your Test Automation.
Sadly I don’t look like this anymore, but let’s pretend that I do.
What is one problem that most of us face with automated functional testing, think about it for a second?
What is one problem that you deal with on a daily basis that causes you a lot of headaches when it comes to functional test automation? Functional test automation?
I already have an idea, just based on my experience, and working with people, and running the whole blog, and do the teaching, I kind of know what problem most people face, but I want to run a poll to see what you guys actually feel the biggest problem with automation is for you.
So, I ran a poll for a few weeks and I got 35response, which is not the most statistically significant number, but I think it’s a good representation of what you guys think.
I feel that if we had much more responses the trend would only further be exaggerated.
So the poll that I ran.
I’ve got a…I’ve put 2 questions…
One question that I asked was: what is a problem that you have with test automation?
And, I believe the number 1 problem that people have with test automation, and you believe as well,
are that they are flaky tests, and the number in parenthesis represents how many responses there were for that answer.
And you guys, it was short text answer, so you probably put different kinds of wording, so I just summarized it into several categories.
Another problem that you are having is a lack of knowledge.
Personally, I would call this a problem with test automation per se, I think it’s just a symptom of the IT industry in that.
None of us have enough knowledge.
I’m still learning and reading books, and reading blogs every single day, and I’m going to continue to do so for the rest of my life.
So, personally, I wouldn’t really consider that a problem but, I can see what you mean.
Another problem that you have is frameworks, and I can definitely see that.
I can see that you are having problems with frameworks and design them.
I personally have problems with them every single day.
Still always trying got improve it, it’s a never-ending improvement, just like the lack of knowledge.
Our next, you guys said the synchronization, and I can definitely understand why synchronization is a problem for a lot of you.
However, I don’t think that is necessarily a problem with test automation, I think it’s moreover a the root cause, of a bigger problem, which is flaky tests.
Right, flaky tests can happen for multiple reasons, like synchronization problems, element identification, problems, and many other problems along the way.
So I think synchronization actually feeds into the flaky tests because if you have problems with your synchronization and application are not loading properly, what’s going to happen?
Well, the test is going to fail inappropriately or pass inappropriately.
Again, that’s a flaky test.
So, I do feel that synchronization feeds into the flaky tests.
And finally, there were a bunch of other responses that didn’t really have more votes than one.
People complained about how much it costs to get started with test automation, license acquiring,
how the process is extremely long to get tools, and many other random problems that didn’t really fit into anyway.
To further convey my point, I ask you a second question