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 learn why parallel testing is great.

Selenium Tutorial – Fast Tests Execution Why is parallel test great

So before we dive right in. Let me give you guys a quick introduction to what parallel testing is and why it is so beneficial. Now let’s imagine this red line is a test. OK it’s an automated functional tests that you wrote. And let’s imagine that you have many of these tests. OK. So each one of these is a test and all of these tests combined are a test suite. OK. This is a test suite that you need to run on a regular basis a standard approach to doing this would be to take this test suite put it into some build system.

Maybe like I don’t know some kind of a build system that’s a build system and it’s going to run one test at a time and then give you an output and then it’s going to run another test and it’s going to give you another output. OK. Results whatever then it’s going to run another test. And that’s going to give you a third output.

So all of these tests they take a pretty long time to run. Why. Because every test is a PS.. In addition to the entire sum of the length of the test suite that it takes to run. So for example if this takes 1 minute to run this takes two minutes to run and this takes one minute and 15 seconds Suran the total amount of time required for your test suite to run is four minutes and 15 seconds. And the more tests you continue to add to this the longer this time gets. And at some point this becomes into hours or possibly even days of running to us sweets which is not realistic at all.

Imagine if you had to wait four days for your results after a cold change to figure out what’s going on with that actual code. That’s where parallel testing comes into play instead of a sequential run order. That standard we can execute these tests their own VI Elmes or their own servers so that they can run in parallel. So rather than putting it all into a single build system each one can have its own process on which it runs and together they can all output the results as soon as the test is done.

And this is very advantageous because as opposed to running a test one by one we can run all of the tests together at the same time depending on your resources right. If you’re running it locally you can only run so many tests at once. Maybe I don’t know 10 if you’re running it in somewhere like the cloud.

You can run like a hundred or thousand tests at once. And at that point your entire test suite runtime will only be as long as your slowest test. Right. If this test takes three minutes and this one takes one minute and another one takes two minutes. All three of these tests are going to run.

Yes all three of these tests are going to run in three minutes because that’s how long it took for this test to run. DSS will be finished before but this one will continue to be running. And then the fact that these are finished before you can probably insert in other testing to hear and utilize all of those processes very efficiently.

So you can see how our tests we time can be significantly decreased. We’re here as opposed to running in four minutes and 15 seconds. It would be down to two minute over a hundred percent efficiency savings just with these three tests. And then if there were a much more it would be magnitudes faster and that’s why people loves automated software testing using parallel testing methods. And that’s why I want to teach you guys how to do that.

It’s a huge return on investment for your company and it helps you get you a faster feedback from your automated software tests. And that’s faster feedback allows you to take action on your development faster which is something that the entire industry is always striving towards.

Nikolay Advolodkin is a self-driven SDET on a lifelong mission to create profound change in the IT world and ultimately leave a legacy for his loved ones, community, and the world at large. Today, he serves as the CEO and Test Automation Instructor at UltimateQA.com and contributes informative articles to leading test automaton websites like SimpleProgrammer.com and TechBeacon.com

Pin It on Pinterest

Share This