Skip to main content

Visual Studio 2015 Update 1–Parallel Test Execution

If you are still looking for an excuse to start installing Visual Studio 2015 Update 1, here I got you one: a new feature that existed before but is now finally back in the box is Parallel Test Execution.

What is it?

From the release notes:

The Visual Studio Test Platform introduces support parallel execution of test cases.

Parallel test execution leverages the available cores on the machine, and is realized by launching the test execution engine on each available core as a distinct process, and handing it a container (assembly, DLL, or relevant artifact containing the tests to execute), worth of tests to execute. The unit of scheduling is the test container. Within each container, the tests will be executed as per the semantics of the test framework. If there are many such containers, then as processes finish executing the tests within a container, they are handed the next available container.

Parallel execution is supported through all launch points - CI, command line (CLI) and the IDE (Test Explorer, CodeLens, various “Run” commands, etc.), and the Test Explorer indicators track the progress of tests executing in parallel.

Getting started
  • Open Visual Studio 2015(don’t forget to install Update 1 first Glimlach)
  • Open the solution containing the tests.
    • Note that in order to leverage the Parallel Test Execution features, tests should be split out over multiple ‘containers’(assemblies)
  • Go to Test –> Test Settings –> Select Test Settings File
  • Select the .testsettings file you want to use.
    • If you don’t have a .testsettings file yet, just create an empty xml file and change the extension to .testsettings

clip_image001

  • Open the file in Visual Studio via File –> Open—> File… –> Open With(click on the small arrow next to the Open button) –> XML Editor
  • Paste the following code:
  • Change the MaxCPUCount value according to the following rules:
    • ‘n’ (where 1 <= n <= number of cores) : up to ‘n’ processes will be launched.
    • ‘n’ of any other value : The number of processes launched will be as many as the available cores on the machine.
  • Now run your tests…

Remark: I noticed that it only worked for MSTest. When using NUnit or XUnit no tests were executed.

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.