What will you learn in this course?
Are you struggling with working with HTML using Selenium WebDriver? Do you know how to easily identify and manipulate an element using Selenium WebDriver? How about performing a drag n’ drop on an element? If not, then these are just a few of the questions that will be answered in this course.
This course is a complete guide on working with web elements in Selenium WebDriver! Once you are finished with this course, you will know how to work with any web elements, anytime, on any web application.
In this course from Ultimate QA, you will learn:
– Basics of HTML
– All the different locator strategies for Selenium WebDriver
– How to identify web elements using Selenium WebDriver
– Master XPath
– Navigation with Selenium WebDriver
– Web element manipulation
– Web element interrogation
– Mouse and keyboard actions with Selenium WebDriver
– Performing actions such as drag n’ drop, drawing, hovering
– Implicit and Explicit waits
– How to properly handle element identification so that your tests are not flaky
– Expected Conditions in Selenium WebDriver
What will you learn in this lecture?
In this video, we will go through the conclusions regarding recorded tests of the page objects in test automation course.
Selenium Tutorial – Page Objects in Test Automation Conclusions regarding recorded tests
Let me reemphasize a few points very quickly.
The main point I don’t want to make to you and that kind of creator’s score sheet to keep track of all this is how many tests actually need to be updated whenever there is a change in our application on their test or any kind of environmental change. And so here I placed a bunch of change agents and then on the right hand side I’m going to display how many recorded tests actually need to be changed as a result of the change agents on the left. So if we change something like the driver we need to update all of the tests basically for everything for you or else for locators usernames and passwords and synchronization issues basically with record and replay. The main point is that it sounds extremely attractive that you can click a record button perform a few actions and then rerun your tests after that and it makes it seem really easy. But the problem is that it is not stable as you could see even after I recorded the initial functional test. I still had to make a few changes to it just in order to get it to run initially. And that happens all the time. So that’s the main point is that I’ve recorded and replay although it does sound attractive it is not stable at all because you need to keep up with too many changes and to update all of the tests. Anytime there’s any kind of change.
So now knowing that knowing that maintenance for recorded tests is extremely tough What is it that you can do to improve your automated functional tests and to take them from a recorded level where a ton of changes can break your automated functional tests and decrease and insulate your tests from all of those changes so that you don’t have to update as many tests at once.