Parallel test execution involves running a suite of automated tests in parallel as opposed to sequentially. You don’t execute your tests one by one. Rather, you take the entire batch and split it up amongst multiple servers so that each server can run a single test at a time. This techniques has some fantastic advantages to improve your overall software development life cycle.

First, running your tests in parallel can significantly decrease your execution time. If you have enough resources to run all of your tests at once, then the duration of the test execution will last only as long as your slowest test. For example, if you have 100 tests and 100 virtual machines on which to run these tests, then dividing them in parallel will allow you to run 100 tests at once. If your slowest test takes two minutes to run, then that is how long it will take for the entire test suite to execute.

Therefore, in this tutorial, I am going to teach you how to do the following:

  1. Run automated functional tests through Selenium Webdriver in parallel on your computer.
  2. Run automated functional tests through Selenium Webdriver in the cloud using BrowserStack.
  3. Run automated functional tests through Selenium Webdriver in the cloud using Sauce Labs.

Running these 100 tests sequentially will take you magnitudes of times longer because you can only execute one test at a time. Therefore, you need to add all of the test run times together to understand how long that will take. If we assume that each test takes two minutes to run, then running them sequentially will take 200 minutes of run time. That’s a 5000% difference!

The second advantage that parallel test execution has over sequential test execution is that it gives your team a faster feedback loop. If your test suite can execute faster, then your team can have feedback faster on which to act upon. This is an amazing thing that the entire IT industry is shifting towards. Continuous delivery wouldn’t be possible if your  entire test suite needed 10 hours to execute.


I am making the assumption that you have the following:

  1. Visual Studio installed
  2. General knowledge of C#
  3. Understanding of Selenium Webdriver

If you need any extra help throughout the tutorial:

How to Execute Automated Tests in Parallel Locally

Create a Class Library project in Visual Studio.

Create a Class Library project in Visual Studio.

Go to NuGet package manager to install appropriate packages.

Go to NuGet package manager to install appropriate packages

Search for Nuget packages

In this step, you are going to install:

  1. Selenium.Webdriver
  2. Selenium.Support

The package source should be set to “”.

Productivity Tip: To save a little bit of time, you can install the Selenium.Support package which will automatically install the Selenium.Webdriver.

Search for Nuget packages

Check Your References

If you installed the Nuget Packages successfully, you will see them in the “References” section of your Solution Explorer.

Check Your References

Install Nunit Nuget Package

Also, install Nunit Nuget package, so we can execute our tests through NUnit. At this time, I had version 3.0.1.

Caution: You will need an NUnitTestAdapter to be able to execute your automated tests through Visual Studio. However, installing v 2.0 of the NUnitTestAdapter from the Nuget will not work. Instead you need the Extension! (At least it didn’t work for my configuration of Visual Studio 2015. I spent hours troubleshooting this problem, and found a solution that I will discuss later. Keep this in mind, so you do not go through the same nightmare that I faced.)

Install Nunit Nuget Package

Install Nunit3 Test Adapter Extension

This step is mandatory if you are running the same exact setup as I am. This will allow us to actually run NUnit tests from Visual Studio.

1. Go to “Tools.”

2. Click “Extensions and Updates.”

Install Nunit3 Test Adapter Extension

Search for “Nunit”

1. Click “Online.”

2. Search for “Nunit.”

3. Install “Nunit3 Test Adapter.” Because we installed NUnit 3 Nuget package, we need the NUnit 3 Test Adapter. Seems logical to me, and I would assume you need to match the NUnit Test Adapter version to your NuGet NUnit version as well. However, since I only have Visual Studio 2015, I cannot guarantee this.

Search for "Nunit"

Check References

Look at your references and make sure that you have all of the appropriate Nuget packages installed: WebDriver, WebDriver.Support, and Nunit.

Check References

Run Your Tests Using F5

When you attempt your tests, you will get the error below. This is simply because you created a project of type Class Library. This project does not contain a Main method for our application to enter and start running.

Let’s fix this.

Run Your Tests Using F5

Add the [TestFixture] Attribute to Your Test Class

This tells Nunit that this class contains tests and, optionally, setup or teardown methods.

My Resharper is smart enough to pull in all of the references into my tests for Nunit. If you don’t know about Resharper, learn it and drastically improve your coding speed.

However, if right now your goal is to get through this parallel testing tutorial and you only have Visual Studio 2013 or earlier, you will need to add the following line to the top of the references(without the quotes):

“using NUnit.Framework;”

My Visual Studio 2015 was smart enough to figure this out as well. Using “Ctrl + .”, you can have Visual Studio fill in those details.

Add the [Test] Attribute to Your Test Method

This will tell the testing framework what is a test that should be ran.

My final code can be found below. You can always download the code for free as well if you want it for reference. If you want video tutorials on this, that’s available for free as well.

Run Your Nunit Test

You should now be able to run this test, using the updated code above. Build the code first so that Visual Studio can find the tests. Then, in the Test Explorer pane, you will be able to see your single test called Test1. Press the “Run All” link to run all of the tests. Success is so sweet!  Run Your Nunit Test

How to Run Tests in Parallel

Caution: The current version of NUnit (3.0.1) cannot run multiple tests inside of a test class in parallel. It will only run those sequentially; trust me, I tried. Therefore, if you want to run your tests in parallel, you will need a single test class for each test. Copy over your test to a different class. Update your second test to be a little different than the first. My code looks like this:

Add the [Parallelizable] attribute to each of your classes. This will allow your tests to run in parallel.

Build your code so that your new test is discovered in the Test Explorer menu. I do this with F6 in Visual Studio 2015. You are now ready to run your parallel tests.

How to Run Tests in Parallel

Execute Parallel Tests

Go ahead and run your tests in parallel in your local browsers by pressing the “Run All” button in your Test Explorer. One test should pass and one should fail if you were following along with my tutorial.

That’s it!

You have successfully created tests to run in parallel using your local resources.

Execute Parallel Tests

Advantages and Disadvantages of Running Tests Locally


  1. You can run multiple tests at once that are only limited by the hardware of your computer. It will decrease execution time, because your longest run will be as long as your slowest test.
  2. If this is all you have available, then this is much better than running one test at a time sequentially.


  1. One of the biggest problems with local testing is that you have to maintain the software. Therefore, you will need to maintain the latest versions of Selenium Webdriver and all of the browsers. This is an extremely painful process. I have problems with this all the time as things get out of sync at some point. If you decide to go the Selenium Grid route and start using multiple virtual machines for this process, you will need to maintain those as well as the updates, configurations, and so on. At the same time, you will need to write frameworks and do your job as a QA Engineer. It’s almost impossible to do all of these well and certainly isn’t worth your time.
  2. You can only run a small number of parallel tests at once on your computer. You need large computing capacities to be able to run 50 browsers at once. Therefore, you are limited by the computing resources that you have.

How Do You Overcome the Disadvantages of Local Parallel Testing?

Do not get discouraged by those disadvantages, however. Having the capability to run parallel tests on your local host is much better than running tests sequentially. Your work environment will dictate what resources are available to you. Therefore, even if you can only run tests in parallel on your local computer, take that option.

Running tests sequentially is the most basic and inefficient way to execute your tests. The next logical upgrade is to run your tests locally, in parallel. After this, you can move to running tests in parallel on multiple servers. Finally, the most efficient and my favorite way to execute tests is covered below.

To overcome the annoying problems of having to maintain all your own hardware and software, you can go to the cloud. There are amazing services like SauceLabs or BrowserStack that help you do this.

Testing in the cloud is really amazing. Some of the benefits that you get are:

  1. Test in parallel with as many VMs as you want. Run 1000 parallel tests if you have the money.
  2. Test in any combination of browser and OS. They have over 700 browser/OS combinations that you can run against. You can even test mobile.
  3. They automatically record logs, screenshots, and videos for you. No work on your end. This makes debugging for Automation Engineers and Developers a breeze.
  4. They have Continuous Integration plugins for tools like Jenkins, so you can easily set those up.
  5. Nobody needs to waste time maintaining any kind of software or hardware.
  6. Automation Engineers can now spend more time creating tests and less time doing other tasks

Really. Testing with these services will take your automation to a completely different level. It would take me multiple years and multiple resources to be able to achieve such an amazing framework. It’s best to just plug in and utilize the awesomeness that already exists.

How to Execute Selenium Webdriver Tests in Parallel with BrowserStack

What is BrowserStack?

BrowserStack is a cloud based service that allows you to do automated software testing using Selenium Webdriver. They maintain a large matrix of browsers and operating systems to make cross browser functional testing easier. At the time of this post, they had over 700 possible combinations. Basically, you have the capability to run on Mac, Windows, Android, iOS, and many combinations, simply by passing in the correct configuration.

Personally, I love running my automated Selenium Webdriver tests in the cloud. Compared to running them locally, the advantages are light years ahead. Give it a try; the difference is drastic.

Setting up for Parallel Testing in BrowserStack


How to Get Started Using BrowserStack

Any Selenium Webdriver cloud automation system is very similar to running our tests locally. The main difference is that, rather than creating a local driver that points to an executable like FirefoxDriver or ChromeDriver, we create a RemoteWebDriver. We pass in a URI and capabilities to that driver so that we can execute our tests in the cloud.

To set up the code to run BrowserStack tests:

1. Set up another Visual Studio C# Class library project just like before. As always, you can just download my code. But you will have the best retention rates if you actually practice what you learn. It’s best to learn something well one time, as opposed to many times with poor comprehension.

2. From the BrowserStack site, I copied the code snippet that was there to get me started. I will modify it a little to match my needs. However, what you will notice is all of the compilation errors after you paste the code into your solution.

How to Get Started Using BrowserStack

Fix the Compilation Errors

You need to fix these errors before you can proceed.

Productivity Tip: If you have ReSharper, you can quickly do this using their shortcut “Ctrl + Enter.” This will allow you to search for all of the broken directives in Nuget and bypass the process of doing that manually like we did above. Take a look.

Fix the Compilation Errors

Using ReSharper to Fix the Broken Directives

ReSharper can quickly search Nuget and find the packages to help me fix my broken directives. By the way, I am not affiliated with Jetbrains at all. I just really think that their product is freaking sweet, and I give them props!

In less than one minute, I installed three Nuget packages and fixed all of my compilation errors. Now that’s an effective product.

If you don’t have ReSharper, just follow the steps that we did above to download all of the appropriate Nuget packages. These are the same ones that we used for the local automated testing.

Using ReSharper to Fix the Broken Directives

Setting up Tests to Run in Parallel with BrowserStack

1. After all of your compilation errors are gone, make sure to get your username and access key from your BrowserStack account.

Productivity Tip: If you are logged in to BrowserStack and you are copying the code sample that they provide, your access key and username will be present in the code sample, and you do not need to take any further action.

2. Update the Init() method of the class to use the capabilities that we desire. In this case, I am going to make my tests run in different browser and OS combinations.

3. On BrowserStack’s help page, they have a section called “Setting your operating system, browser, and screen resolution” that allows you to pick your browser and OS combinations and then gives you a code snippet to paste into your test. Pick whatever combination you want and paste that into your Init() method.

4. Copy the entire class and create another test. Rename the class and the methods appropriately to help you when running the tests. Take a look at the code sample below if you are confused.

5. Do this as many times as you want. Remember, each class will represent a test so that NUnit can run in parallel through BrowserStack. Rename all of the classes and methods as necessary. Also, these tests aren’t as efficient as they could be. I am simply demonstrating how to run tests in parallel. You can always take it a step further and abstract out the Init() and Cleanup() methods to a base class and decrease the redundancy.

If you are new to C# and don’t understand how to structure classes, you can learn that in the Complete Selenium Webdriver with C# Course.

6. Finally, add the [Parallelizable] attribute on each of the classes like before.

7. Don’t forget to update your username and access key before running the tests.

Your code is going to look like the sample below. As always, you can download the code as well.

How to Run the Parallel Tests in BrowserStack

1. Build your solution so that the Test Explorer can discover the new tests that you just added. 2. Right click and select “Run Selected Tests.”How to Run the Parallel Tests in BrowserStack

Tests Running in Parallel

Check that out! Four awesome tests running in parallel. My subscription allows me to run up to 40 tests in parallel. Play around with BrowserStack a bit. Notice how our tests automatically have recorded video, text logs, and visual logs. We didn’t need to do anything to get this capability. They just include it.Tests Running in Parallel

How to Run Tests in Parallel Using Sauce LabsHow to Run Tests in Parallel Using Sauce Labs

What Is Sauce Labs?

Sauce Labs is very similar to BrowserStack. It is also a cloud based system that allows you to execute automated test cases in the cloud. They host the infrastructure and allow you to run your tests on hundreds of different operating systems and browsers. I prefer Sauce Labs to BrowserStack for a few reasons:

  1. They were established earlier and have an overall better platform.
  2. Their documentation is excellent and makes integrating with their technology really easy.
  3. Overall, they have more features than BrowserStack.

But either of these solutions is light years ahead of local functional GUI testing with Selenium Webdriver. So take what you can get.

Getting Started with Sauce Labs

  • As with most of these tools, you need an account. Get a Free Trial if your company does not have accounts.
  • The documentation on Sauce Labs is really great. You can follow it to get your code running.

Basically, you do everything that we did before, by installing all of the Selenium Webdriver Nuget packages and NUnit.

Copy Source Code and Fix Compiler Errors

    1. Copy the source code on their help page and paste that into your class in Visual Studio. You will now have a lot of compiler errors. In my example, I see 41.
    2.  Just like before, allow your intellisense to help you fix these errors. Again, this was just an installation of Nuget packages, updating the test namespace, and making sure that the appropriate user and key are ready for Sauce Labs.

My final code looks like this and can be downloaded as well:

Where to Get the Username and the Access Key

When you are logged into Sauce Labs, you can get the access key and the username at the locations shown in the image. Update the code with the appropriate values for your personal account.

If you look at my code again, you will notice that I am using local environment variables to store my username and password. This is actually something that I learned recently from Dave Haeffner through a webinar. This is awesome because my code will always run locally. Also, I can share the code with you without needing to change it to mask my username and password.

Where to Get the Username and the Access Key

Final Requirements Check

Before your run, make sure that you have all of this in place:

1. The correct code downloaded.

2. Nuget packages for Webdriver and Nunit installed.

3. NUnit Extension installed.

4. Your username and password saved to environmental variables. Or, you can just hardcode them into your code.

5. All your tests have the appropriate attributes: [Test] for the tests and [Parallelizable] for classes. If you used the code that I provided, this shouldn’t be an issue. If you create your own code, keep this in mind.

How to Run Webdriver Tests in Parallel Using Sauce Labs

1. Build your code so that the Test Explorer can see all of your tests.

2. In the Test Explorer, highlight the tests that you want to run. Since we are working with Sauce Labs, let’s select the Sauce Labs tests.

3. After they are selected, right click and do “Run Selected Tests.”

How to Run Webdriver Tests in Parallel Using Sauce Labs

Where to See the Results for the Sauce Labs Run

Look at your Sauce Labs dashboard. You will see your two tests running in parallel. Take a look at the time stamps.

If you really want to put what you learned to the test, why don’t you add more tests to the Sauce Labs test suite and see if you can get them all to run in parallel?

Where to See the Results for the Sauce Labs Run

Some Cool Sauce Labs Features

The reason that I like testing in the cloud way more than testing locally is because of all of the amazing features that these services offer. If you click on one of the tests, you can get a Command Log, Screenshots, Videos, Metadata, Selenium Log, and Interactive Sessions, all of which you can download.

In all of my years of automated software testing, I could never dream of having such sexy functionality built into my framework. With Webdriver and Sauce Labs, it’s really easy, and you get it out of the box.

Play around with these tabs, explore. It’s super cool what you will see 🙂

What Error Message?

Nunit.Core.UnsupportedFrameworkException: Skipped loading assembly ‘{assembly name}’ because it references…

If you run into this error, it’s because you are trying to use Resharper to run your tests. I made this mistake myself. Instead, use Visual Studio to execute your tests, and the tests will run fine through the NUnit extension.


In conclusion, doing parallel testing with Selenium Webdriver has many benefits, like decreasing your execution time of the test suite and decreasing the length of the feedback loop that your tests provide. These benefits help to drive higher quality software through more efficient means, something that I strive for every day.

If you have the choice, try to execute your parallel tests in the cloud. The benefits that you receive like logs, videos, screenshots, and your work history are unparalleled to anything that you will be able to create yourself. All these extra services will help to make you more efficient by helping you to debug and allowing you to spend more time actually covering new functionality.

At this point, feel free to try this out on your own. Automate whatever tests you want and have them run in parallel. You can practice functional automated software testing on this practice page.

Thanks for taking your time to read my post. Feel free to leave any comments, questions, or insults. Again, here are extra resources if you require them: