Execute tests
JetBrains Rider provides several ways to execute unit tests. Whichever way you choose, execution progress, test results, and output are displayed in the Unit Tests window , coverage results are shown in the Unit Test Coverage window .
Before running coverage analysis or performance profiling, make sure that the PDB information exists for all target assemblies. The safest choice would be to build your code with the Debug build configuration.
Different ways to run, debug, or cover unit tests
Start test execution
Use one of the ways to execute tests in the current document.
Use one of the ways to execute tests in the project/solution.
If there are existing unit test sessions, you can run, debug, or cover some or all tests in a session:
Select tests that you want to execute in the session tab of the Unit Tests window and click Run Unit Tests
Ctrl+;, R/Debug Unit Tests 
Ctrl+;, D on the toolbar.To run all tests in the session, click Run Current Session
Ctrl+;, Y on the toolbar or alternatively, choose from the main menu.To keep automatically starting and running selected tests until one of the tests fails, choose Run Selected Tests Until Failure from the session's context menu, or from the main menu.
As tests are running in a unit test session, the progress icon is displayed next to the currently executing test. You can run multiple unit test sessions simultaneously. However, when you debug tests, only one test session can be executed at a time.
Stop test execution
Click Stop Execution
.png "ThemedIcon.StopTest.Screen.(Gray).png")
on the toolbar to abort execution of the tests.JetBrains Rider will send the signal to the test runner to stop execution. Depending on the test framework, the execution can be aborted immediately, or the runner may try to finish the current test and stop after that.
If the test runner continues executing the current test, the Stop Execution icon changes to
. You can click it again to force quit the test runner process.
If necessary, you can always repeat execution or coverage analysis of the tests that you executed last by clicking Repeat Previous Run .png "ThemedIcon.Rerun.Screen.(Gray).png"){kind=icon}
on the toolbar, pressing Ctrl+;, T or choosing from the menu.
You can also re-run tests that failed by pressing Ctrl+;, F or choosing from the menu.
Run configurations for test sessions
JetBrains Rider automatically creates a new run configuration for each test session. The created run configuration stays synchronized with the corresponding session until you close the session in the Unit Tests window.
Customize execution process
By default, JetBrains Rider uses unit test project settings to define which .NET Framework version and processor architecture should be used when executing tests.
When tests in your project use (sometimes indirectly or implicitly) an assembly based on CLR2 and your project already targets CLR4, errors may occur during test execution. You can avoid such situation, by specifying explicitly what CLR (.NET Framework) should be used. To do so, use the Default .NET Framework version selector on the page of JetBrains Rider settings Ctrl+Alt+S. This preference affects tests running under NUnit, XUnit and MSpec test frameworks. It has no effect on tests running under MSTest yet.
You can also change the platform architecture (32-bit or 64-bit) using the Default platform architecture selector on that options page.
If necessary, you can override these settings for specific unit test session using the Session Options 
selector on the toolbar.