Test Runner


Shadow-copy assemblies being tested	When this option is enabled, assemblies that participate in tests are copied to a temporary directory. This allows you to edit and rebuild test assemblies even while the related tests are running. You can choose between two options of shadow-copying: Native — enables the shadow-copying mechanism of the test framework, which normally only copies assemblies. Advanced — by default, this mechanism copies all relevant files and subdirectories from the directories where the assemblies are compiled. When you select this option, the masks of the copied files appear in the File mask field, where you can further customize what should be shadow-copied.
If the test runner process does not exit after [x] seconds	These options let you configure the way JetBrains Rider decides when the test runner process is hung and what to do in that case.
If the spawned processes do not exit after [x] seconds	By default, JetBrains Rider maintains a list of all processes that are launched by the executed tests. If some of these processes do not exit after the test execution is over, JetBrains Rider will suggest that you terminate the process. These options let you configure the way JetBrains Rider decides when a spawned process is hung and what to do in that case. If you choose Ask what to do, you will be able to decide whether to terminate each spawned process that hung. JetBrains Rider will remember your choice and add such child processes to the list on this options page. If you want to cancel the previously selected action for a specific process, remove it from the list.

Shadow-copy assemblies being tested

When this option is enabled, assemblies that participate in tests are copied to a temporary directory. This allows you to edit and rebuild test assemblies even while the related tests are running. You can choose between two options of shadow-copying:

Native — enables the shadow-copying mechanism of the test framework, which normally only copies assemblies.
Advanced — by default, this mechanism copies all relevant files and subdirectories from the directories where the assemblies are compiled. When you select this option, the masks of the copied files appear in the File mask field, where you can further customize what should be shadow-copied.

If the test runner process does not exit after [x] seconds

These options let you configure the way JetBrains Rider decides when the test runner process is hung and what to do in that case.

If the spawned processes do not exit after [x] seconds

By default, JetBrains Rider maintains a list of all processes that are launched by the executed tests. If some of these processes do not exit after the test execution is over, JetBrains Rider will suggest that you terminate the process.

These options let you configure the way JetBrains Rider decides when a spawned process is hung and what to do in that case.

If you choose Ask what to do, you will be able to decide whether to terminate each spawned process that hung. JetBrains Rider will remember your choice and add such child processes to the list on this options page. If you want to cancel the previously selected action for a specific process, remove it from the list.

Environment variables

In this area, you can configure a list of Name-Value pairs of environment variables that would be passed to the process started by the unit test runner and to all its child processes.

These environment variables will override variables with the same names defined in your system, if any.

Depending on whether these environment variables contain sensitive information or not, you can save them either in the 'Solution personal' or in the 'Solution team-shared' settings layer.

Test Settings

Choose where JetBrains Rider should look for test settings:

Specify a custom test settings configuration (.runsettings/.testsettings file within your solution).

Diagnostics

Use these options if you want to troubleshoot potential problems with unit text execution. All diagnostic information will be saved in the corresponding files in the log folder, which you can open by choosing Help | Diagnostic Tools | Show Log in Explorer from the main menu.


Capture output	Select this checkbox to write the output of the test runner process and all its child processes to a file.
Log level	Select a logging level to write log messages of the corresponding verbosity to a file.

Last modified: 30 July 2024