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

Take This Entire Course for Free

What will you learn in this lecture?

In this video, we will go through the How to install NUnit Test Adapter of the Fast Tests Execution course.

Selenium Tutorial – Fast Tests Execution How to run selenium tests in parallel using sauce labs

So let’s go ahead and analyze this last lapse test which is very similar to the browser stack test. You guys can see here how that looks also in in its method and actual test and then a clean up method. And of course this isn’t the best it’s not following the best design patterns right. If you’ve got some kind of a framework you can of course put the set up and tear down and some kind of a base class that from which our test classes could inherit from and then we don’t have to keep recoating there. But that’s not the purpose of this Tauriel. The purpose of this tutorials obviously for me to teach you how to do parallel testing. So anyways Soest labs the way they had their code configured is passing in all of the browsers and operating systems is through the test Ficke attribute. And then it goes to the constructor which sets the fields through the constructor and then that gets passed and into the desired capability’s class. So I actually like that a lot more if you guys remember the browsers like that a little bit differently where we were just setting our desired capabilities here. You can also passing through a config file as well which is actually really cool and probably a good way to do it so that you can control your tests externally. And so that’s died.

And then there’s the set up which they also do the similar thing where they have a username and an access key as does browser stack and then the actual tests of course and then the tear down method in which they do a little bit of a clean up and display a message in their results. So that’s that’s the selenium test but obviously not so relevant unless we’re making a parallel run.

So I’m going to do the same exact things as before. I’m going to take this class which let me rename again. You see the problem with Visual Studio is why doesn’t rename the files automatically going to copy this. I’m going to paste it. Double Click here to rename it. I’m just going to do two tests at once. Rename the file or the class rename the constructor and that’s pretty good. I guess we can change this to run on Chrome 40 and the Windows 8 and the rest is all OK it’s parallelizable and it’s got everything here. If we look at the test explorer we don’t see Soest test yet. So of course we need to build so that our test Explorer finds our tests give it a second it’s built succeeded. So now we can see Passau swan on the run tests us too. I’m going to go ahead and run them both run select a test see running them together going to pull a browser stack here go back to my account and give it a second look at that. Running two tests you want to view full screen you can bet it’s probably already finished. You can see two tests were ran together. Look at this time. They started about five seconds apart. So you can pretty much see that parallel. Right. And then one test ran longer than any other. And then of course you can sit in here and analyze you can see they ran on different browsers different operating systems which is really cool. And again another benefit of parallel testing and the why.

I’m a big fan of it and why I encourage you guys to learn this technique so that you can help your jobs as well.

 

Pin It on Pinterest

Shares
Share This