RunSettings and xunit.runner.visualstudio

Set this value to determine whether App Domains are used. By default, they will be used when available (the ifAvailable value). If you set this to required, it will require that app domains are available; if you set this to denied, it will not use app domains. Note that App Domains are only supported with .NET Framework tests, and only with tests linked against xUnit.net framework v1 or v2.

Valid values: required, ifAvailable, denied
Default value: ifAvailable

Set this value to true to include diagnostic information during test discovery and execution. Each runner has a unique method of presenting diagnostic messages.

Valid values: true, false
Default value: false

Set this to true to enable skipped tests to be treated as errors.

Valid values: true, false
Default value: false

Set this value to true to include internals diagnostic information during test discovery and execution. Each runner has a unique method of presenting diagnostic messages. Internal diagnostics often include information that is only useful when debugging the test framework itself.

Valid values: true, false
Default value: false

Set this value to enable long-running (hung) test detection. When the runner is idle waiting for tests to finished, it will report that fact once the timeout has passed. Use a value of 0 to disable the feature, or a positive integer value to enable the feature (time in seconds).

NOTE: Long running test messages are diagnostic messages. You must enable diagnostic messages in order to see the long running test warnings.

Valid values: Any integer >= 0
Default value: 0 (disabled)

Set this to override the maximum number of threads to be used when parallelizing tests within this assembly. Use a value of 0 to indicate that you would like the default behavior; use a value of -1 to indicate that you do not wish to limit the number of threads used for parallelization.

As of v2 Test Framework 2.8.0+ and xunit.runner.visualstudio 2.8.0+, you can also use the multiplier syntax, which is a multiplier of the number of CPU threads. For example, 2.0x will give you double the CPU thread count. You may also use the string values unlimited and default in place of the integer values -1 and 0, respectively.

Valid values: Any integer >= -1, a multiplier, unlimited, or default
Default value: the number of CPU threads in your PC

Set this to override the default display name for test cases. If you set this to method, the display name will be just the method (without the class name); if this set this value to classAndMethod, the default display name will be the fully qualified class name and method name.

Valid values: method, classAndMethod
Default value: classAndMethod

Set this to automatically perform transforms on default test names. This value can either be all, none, or a comma-separated combination of one or more of the following values:

• replaceUnderscoreWithSpace Replaces all underscores with spaces
• useOperatorMonikers Replaces operator names with matching symbols
  • eq becomes =
  • ne becomes !=
  • lt becomes <
  • le becomes <=
  • gt becomes >
  • ge becomes >=
• useEscapeSequences Replaces escape sequences in the format Xnn or Unnnn with their ASCII or Unicode character equivalents. Examples:
  • X2C becomes ,
  • U1D0C becomes ᴌ
• replacePeriodWithComma Replaced periods with a comma and a space. This option is typically only useful if methodDisplay is classAndMethod.

Valid values: all, none, or comma separated flags
Default value: none

Set this to true to disable automatically enabled reporters (for example, reporters that automatically detect and enable support for AppVeyor, TeamCity, or Azure Pipelines). This is typically only used in debugging scenarios when trying to determine why tests aren't properly reporting into your CI environment.

Valid values: true, false
Default value: false

Set this to change the way tests are scheduled when they're running in parallel. For more information, see Running Tests in Parallel. Note that the algorithm only applies when you have enabled test collection parallelism, and are using a limited number of threads (i.e., not unlimited or -1).

Valid values: conservative, aggressive
Default value: conservative

Set this to true if this assembly is willing to participate in parallelization with other assemblies. Test runners can use this information to automatically enable parallelization across assemblies if all the assemblies agree to it.

Valid values: true, false
Default value: false

Set this to true if the assembly is willing to run tests inside this assembly in parallel against each other. Tests in the same test collection will be run sequentially against each other, but tests in different test collections will be run in parallel against each other. Set this to false to disable all parallelization within this test assembly.

Valid values: true, false
Default value: true

Set this to true to pre-enumerate theories so that there is an individual test case for each theory data row. Set this to false to return a single test case for each theory without pre-enumerating the data ahead of time (this is how xUnit.net v1 used to behave). This is most useful for developers running tests inside Visual Studio, who wish to have the Code Lens test runner icons on their theory methods, since Code Lens does not support multiple tests from a single method.

Valid values: true, false
Default value: true

Set this value to use a different reporter than the default. There are four reporters that ship with xunit.runner.visualstudio with behavior that deviates from the default:

• quiet will only print failure information
• verbose will print messages when tests start abd finish
• json will print messages in a JSON format
• teamcity will print TeamCity-formatted messages
• silent turns off all messages (xunit.runner.visualstudio 2.5.4+)

Note: In order to see the reporter output, you will need to change the verbosity level of the console reporter. In Visual Studio, you can do this by opening the Options settings, navigating to Test > General, and the setting the drop down under "Logging Level" to "Diagnostic" (the logs in Visual Studio will appear in the Output window, under "Tests"). From the command line, you can pass --logger "console;verbosity=normal" on the dotnet test command line.

Valid values: quiet, verbose, json, teamcity
Default value: unset

Set this to true to use shadow copying when running tests in separate App Domains; set to false to run tests without shadow copying. When running tests without App Domains, this value is ignored.

Valid values: true, false
Default value: true

Set this to true to stop running further tests once a test has failed. (Because of the asynchronous nature of test execution, this will not necessarily happen immediately; any test that is already in flight may complete, which may result in multiple test failures reported.)

Valid values: true, false
Default value: false