JetBrains Rider 2019.3 Help

Execute Tests and Analyze Results

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

There are following ways to run, debug, or cover unit tests:

  • 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 Run Unit Tests Ctrl+U, R / Debug Unit Tests Debug Unit Tests Ctrl+U, D on the toolbar.

    • To run all tests in the session, click Run Current Session Run Current Session Ctrl+U, Y on the toolbar or alternatively, choose Tests | Run Current Session from the main menu.

    • To continuously run selected tests in the session until one of the tests fails, choose Repeat Tests Until Failure from the session's context menu, or Tests | Repeat Tests Until Failure from the main menu.

As tests are running in a unit test session, the Stop Execution ThemedIcon StopTest Screen Gray button becomes active. You can click this button to abort execution of the tests. You can run multiple unit test sessions simultaneously. However, when you debug tests, only one test session can be executed at a time.

If necessary, you can always repeat execution or coverage analysis of the tests that you executed last by clicking Repeat Previous Run ThemedIcon Rerun Screen Gray on the toolbar, pressing Ctrl+U, U or choosing Tests | Repeat Previous Run in the menu.

You can also re-run tests that failed by pressing Ctrl+U, F or choosing Tests | Rerun Failed Tests in 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.

Analyze execution results and output

When the execution is over, the results are visualized in the Unit Tests window.

JetBrains Rider: Unit test sessions

The output pane (which you can place on the right or on the bottom using the Toggle output position Toggle output position button on the toolbar) displays output of the selected test. If the test is failed, JetBrains Rider also adds short information on the failure and/or displays the stack trace of an exception. You can use clickable links in the output pane to navigate directly to types and methods involved with the failure.

By default, JetBrains Rider wraps long lines in the output according to the current width of the output area. If necessary, you choose not to wrap long lines by clearing the Wrap long lines in Unit Test Session output checkbox on the Build, Execution, Deployment | Unit Testing page of JetBrains Rider settings Ctrl+Alt+S.

On the status bar, you can see the total number of tests in the session as well as number of tests in different states:

By default, tests in all states are shown, but you can click the corresponding icons to filter tests by their state.

Status of each test in the Unit Test Sessions window is displayed with one of the following icons:

ThemedIcon RunningTest Screen Gray

Unit test is currently executing

ThemedIcon TestPending Screen Gray

Unit test is scheduled for execution in the current run

ThemedIcon StatusUnknown Screen Gray

Unit test was not executed

ThemedIcon Success Screen Gray

Unit test passed in the lats test run

ThemedIcon Error Screen Gray

Unit test failed in the lats test run

ThemedIcon Ignore Screen Gray

Unit test was ignored in the last test run

ThemedIcon StatusAborted Screen Gray

Unit test was aborted in the last test run

ThemedIcon StatusInconclusive Screen Gray

Unit test was started but JetBrains Rider could not read the test runner output. This could be a sign of an error occurring in the test runner.

The same icons are used to display status of grouping items (classes, projects, and so on)

The icons are also used on each session's tab to display the overall execution result of the sessions.

The corresponding icons above the test session tree show how many tests are in each of the states. The ThemedIcon UnitSession Screen Gray icon shows the total number of tests in the session.
Using these icons, you can filter the tree so that only tests in the corresponding status are displayed.

When your focus is in the Unit Tests window, you can use simplified shortcuts for unit testing actions. For example, you can use Ctrl+D instead of Ctrl+U, D for debugging selected tests. Here is the full list of extra shortcuts that work in the Unit Tests window:

  • Shift+EnterRun Selected Tests

  • Ctrl+DDebug Selected Tests

  • Ctrl+YRun Current Session

  • Ctrl+FRerun Failed Tests

  • Shift+Alt+InsertCreate New Session

  • Ctrl+Alt+InsertAppend Selected Tests to Session

  • DeleteRemove Selected Tests

  • Ctrl+LRun All Tests from Solution

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 Build, Execution, Deployment | Unit Testing 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 Session Options selector on the toolbar.

Study execution log

Unit Tests window includes test execution log that lets you separate problems related to test execution process from unit tests results.
You will normally need to check execution log if some of your tests have the 'Inconclusive' state after execution, which could be a sign of an error occurring in the test runner.

To check the execution log, click Launch on the Unit Tests window toolbar and choose Show Last Launch Log.
If the test execution ends with a test runner exception, you will see a link to the latest log file.

Last modified: 24 February 2020