TAEF provides a mechanism to execute tests in parallel across multiple processors.

Parallelism Guarantees

  • No two tests not marked as parallelizable will ever be executed concurrently.
  • Parallel tests can be run concurrently with both other parallel and non-parallel tests.
  • All module/class/test setup and cleanup will be run linearly before and after the relevant test in the same process.
  • Module/class setup may be executed in parallel on different processes if the module or class contains at least one parallel test.
  • Parallel execution mode is incompatible with the "/inproc" execution mechanism.

Marking Tests as Parallelizable

Example (native code):

class MyTests


        TEST_METHOD_PROPERTY(L"Parallel", L"true")

As with other general metadata in TAEF, this can be specified at the class or module level & will be inherited by all tests contained within that class or module. For example, to mark an entire assembly as parallelizable you could do the following (outside any class or test specification) in a cpp file compiled into your test DLL:

    MODULE_PROPERTY(L"Parallel", L"true");

This wider-scope can then be overriden at smaller scopes to disable parallelism for particular test cases or classes as follows:

class MyTests

        TEST_METHOD_PROPERTY(L"Parallel", L"false");

Whichever setting is closest to the test method (method metadata is the closest, then class, then module) will be used to decide whether to run this test in parallel with other tests.

Enabling Parallelism at the Command Prompt

Parallel execution is an opt-in feature. While tests may be marked up as parallel, TAEF will continue to execute tests linearly unless parallel execution mode is enabled at the command prompt:

te unittests\* /parallel

Send comments about this topic to Microsoft