Unit Testing
On this page of ReSharper options, you can adjust unit testing settings.
Item | Description |
---|---|
General | |
Default platform architecture | This selector allows choosing a platform to run unit tests on. |
Default .NET Framework version | This selector allows setting .NET version to use when running unit tests. |
Run up to [number of assemblies] assemblies in parallel | Select the number of assemblies to be tested by ReSharper concurrently in parallel threads. |
Skip tests from categories | Type names of test categories to be excluded from the run. The tests associated with the category that you specified are ignored. For more information, see Working with Test Categories |
Unit Test Sessions | |
Save and restore Unit Test Sessions | Select this check box to allow ReSharper to restore unit test sessions when you close and reopen Visual Studio. |
Show log entries with severity | This selector lets you specify which log entries should appear in the execution log in the Unit Test Sessions window. |
Unit Test Output | |
Wrap long lines in Unit Test Session output | Defines how to display long lines in the Output tab in the Unit Test Sessions window. If this check box is selected, long lines are wrapped. |
Limit the number of lines in output to: | Defines how to many lines should be displayed in the Output tab in the Unit Test Sessions window. |
Unit Test Runner | |
Shadow-copy assemblies being tested | If this check box is selected, assemblies being tested are subject to shadow-copying. So even while the tests are running, assemblies can be rebuilt. |
Use separate AppDomain for each assembly with tests | This option applies to MSTest and NUnit tests and lets the test runner start each test assembly in its own Application Domain. It may come in handy in the following situations:
|
Check for hanging test execution | By default, ReSharper notifies you if there is no response from the test execution process. |