Rider Help

Unit Testing

File | Settings | Build, Execution, Deployment | Toolset and Build for Windows and Linux
Rider | Preferences | Build, Execution, Deployment | Toolset and Build for macOS
Ctrl+Alt+S /help/img/rider/2017.1/settings.png

On this page of Rider options, you can adjust unit testing settings.

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.
Unit Test Sessions
Save and restore Unit Test Sessions Select this check box to allow Rider to restore unit test sessions when you close and reopen Rider.
Show log entries with severity higher or equal to: This selector lets you specify which log entries should appear in the execution log in the Unit Tests 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 Tests window. If this check box is selected, long lines are wrapped.
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:
  • You need to use different app.config files for different test assemblies.
  • You use reflection in tests.
Check for hanging test execution By default, Rider notifies you if there is no response from the test execution process.
You may want to disable this option if there is some code that could take long when executing after tests are finished (SetupFixture TearDown, Class TearDown).
Last modified: 11 October 2017