If your setup requires some processes started by the tests to continue running, you can clear this checkbox to avoid unnecessary notifications. If some of theses processes do not exit after the test execution is over, ReSharper will suggest you to terminate the process. Resharper has a feature Check for orphaned processes spawned by test runner.īy default, ReSharper maintains a list of all processes that are launched by the executed tests.
This allows, in most cases, for no manual closing of the tool to be required. Previous instance must be manually closed
If a tool is running for the comparison of the current verification (per test), and a new verification passes, the following logic will be applied: Mdi This value can also be set using the DiffEngineTray options dialog. This value can be changed by setting the DiffEngine_TargetOnLeft environment variable to true. Snippet source | anchor Left/Right diff behaviorīy default, when a diff is opened, the temp file is on the left and the target file is on the right.
Setting the DiffEngine_MaxInstances environment variable to the number of instances to launch. This value can be changed: Using an environment variable This prevents a change that breaks many test from causing too much load on a machine. MaxInstancesToLaunchīy default a maximum of 5 tool instances will be launched.
If a tool is running for the comparison of the current verification (per test), and a new verification fails, the following logic will be applied: Auto Refresh If no tool is running for the comparison of the current verification (per test), a new tool instance will be launched.