Configuration Files

Configuration files can be used to configure on a per test-assembly basis.

In these examples, we tell you to use the file name xunit.runner.json. You can also use <AssemblyName>.xunit.runner.json (where <AssemblyName> is the name of your unit test assembly, without the file extension like .dll or .exe). You should only need to use this longer name format if your unit tests DLLs will all be placed into the same output folder, and you need to disambiguate the various configuration files.

The assembly-specific filename takes precedence over the non-specific filename; there is no merging of values between files.

Adding the configuration file

  1. Add a new JSON file to the root of your test project. Name the file xunit.runner.json. Start with a schema reference so that text editors (like Visual Studio & Visual Studio Code) can provide auto-complete behavior while editing the file:

      "$schema": ""
  2. Tell the build system to copy the file into the build output directory. Edit your .csproj file and add the following:

      <Content Include="xunit.runner.json" CopyToOutputDirectory="PreserveNewest" />

Supported configuration items

The schema is online at, which can be set in the JSON file to aid with intellisense from development IDEs like Visual Studio and Visual Studio Code.

Configuration elements are placed inside a top-level object:

  "$schema": "",
  "enum-or-string-key": "value1",
  "boolean-key": true,
  "integer-key": 42
Key Supported Values
[Runners v2.1+]

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 framework v1.x or v2.x.

JSON schema type: enum
Valid values: required, ifAvailable, denied
Default value: ifAvailable

[Runners v2.1+]

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

JSON schema type: boolean
Default value: false

[Runners v2.2+]

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.

JSON schema type: integer
Default value: 0 (disabled)

[Runners v2.1+]

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.

JSON schema type: integer
Default value: the number of logical processors in your PC

[Runners v2.1+]

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.

JSON schema type: enum
Valid values: method, classAndMethod
Default value: classAndMethod

[Runners v2.4+]

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.

JSON schema type: string (comma separated flags)
Valid values: all, none, or comma separated flags
Default value: none

[Runners v2.1+]

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.

JSON schema type: boolean
Default value: false

[Runners v2.1+]

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.

JSON schema type: boolean
Default value: true

[Runners v2.1+]

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 v1.x 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.

JSON schema type: boolean
Default value: true

[Runners v2.1+]

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.

JSON schema type: boolean
Default value: true

Copyright © .NET Foundation. Contributions welcomed at