|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:
|Emulate dotnet test resolve behavior|| You need to enable this option if you get |
In this case, ReSharper test runner will use only one
|Check for orphaned processes spawned by test runner|
By default, ReSharper maintains a list of all processes that are launched by the executed tests. If some of theses processes do not exit after the test execution is over, ReSharper will suggest you to terminate the process.
If your setup requires some processes started by the tests to continue running, you can clear this checkbox to avoid unnecessary notifications.
|Check for hanging test execution|| By default, ReSharper notifies you if there is no response from the test execution process. |
You may want to disable or configure this option if there is some code that could take long when executing after tests are finished (SetupFixture TearDown, Class TearDown).
|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.
Note that you don't have to restart Visual Studio after adding new variables.
Choose where ReSharper should look for test settings:
Use .runconfig/.testsettings specified in Visual Studio. If this option is enabled, ReSharper will auto-detect test settings when possible.
Specify a custom test settings configuration (.testsettings file within your solution).