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 Wiring up the 2nd test in code of the page objects in test automation course.
Selenium Tutorial – Page Objects in Test Automation Wiring up the 2nd test in code
So here I am back in Visual Studio. And of course remember you can do. You can use the techniques for any kind of selenium web drive a binding the Towanda or any kind of automation tool that you want. All these techniques are applicable to any language that you want to use. But again my flavor of choices. So anyway the driver with the C#. So I’m going to go ahead and wire up a test here.
Let me add the test attribute.
The way I like to write my test is I like to use test driven development in order to drive the creation of my automation framework. The reason that I like to use it has driven development is because it allows you to write that test first in English language and then you can implement the code for that actual test. It makes the tests much more readable and allows you to lay out your page object as you need them. Also it follows the Yagami principle that says you ain’t going to need it because it allows you to only code whatever you need at the time which makes your automation very fast and very efficient.
So we can actually copy over a bunch of this actually all of this because it does the log in and Dan and we validate that we are at the dashboard page which is fantastic. And then we need to add a few extra steps of clicking the log in clicking the link that’s going to take us to the course and then validating that the Course is actually opened.
So using the student dashboard page.
I’m going to resume the user interaction course. Does that make sense.
And then of course that’s going to return a page for me that is going to be called.
User interactions course page so of course the compiler is complaining because these methods are not yet implemented. But we’re going to implement them. So when we click the resume user interaction of course that’s going to return and so user interaction of course page.
Let’s go ahead and take a look at that again.
We’re so we’re here the student dashboard resume course. OK. So that’s that. And then we pull up the page. And then we need to validate that the Course is opened appropriately.
And so that’s just an assertion.
So that just an assertion that we’re on the right page. And then there’s an error message just in case this fails. So now we kind of wrote We wired out our test. Now we just need to implement the methods