ReSharper
 
2022.1
Shortcuts: Visual Studio
Get ReSharper
You are viewing the documentation for an earlier version of ReSharper.
  1. Unit testing assistance
  2. Execute tests and analyze results

Execute tests and analyze results

Last modified: 21 July 2022

tip

ReSharper's unit test runner does not allow running two or more tests with the same ID. This rarely happens in practice, but if you do have tests with the same ID, they will appear as a single node in the Unit Tests explorer and Unit Test Sessions window, and only one of them will run.

Note that test frameworks identify tests in different ways. For example, MSTest uses test-methods FQNs but NUnit uses properties of test attributes as test IDs.

ReSharper provides several ways to execute unit tests. Whichever way you choose, execution progress, test results, and output are displayed in the Unit Test Sessions window, coverage results are shown in the Unit Test Coverage window.

tip

Unit testing assistance can be extended with other JetBrains .NET products: you can profile unit tests with dotTrace and analyze code coverage of unit tests with dotCover. These products are included in the dotUltimate license.

Different ways to run or debug 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 or debug some or all tests in a session:

    • Select tests that you want to execute in the Unit Test Sessions 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 ReSharper | Unit Tests | Run Current Session from the main menu.

    • To keep automatically starting and running selected tests until one of the tests fails, expand the selector at the Run Unit Tests Run Unit Tests Ctrl+U R button and choose Run Unit Tests Until Fail.

As tests are running in a unit test session, the execution progress is shown in the status bar under the toolbar of the Unit Test Sessions window and 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.

If necessary, you can enable the Track Running Test Themed icon track run screen gray option on the toolbar. If it is on, the selection in the test tree switches automatically to the test that is currently running and the output panel always shows output of the current test during the execution.

You can also enable the Auto Scroll Output When Running Test Themed icon scroll to bottom screen gray option to follow output of tests as they are running.

Stop text execution

  1. Click Stop Execution Themed icon stop test screen gray on the toolbar to abort execution of the tests.

  2. ReSharper 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.

  3. If the test runner continues executing the current test, the Stop Execution icon changes to Themed icon abort screen gray. You can click it again to force quit the test runner process.

If necessary, you can always re-run the tests that you executed last by clicking Repeat Previous Run Themed icon rerun screen gray on the toolbar, pressing Ctrl+U U or choosing ReSharper | Unit Tests | Repeat Previous Run in the menu.

Analyze execution results and output

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

ReSharper: Unit test sessions

The output pane (which you can place on the right or at the bottom using the Show Output Show Output button on the toolbar) displays output of the selected test. If the test is failed, ReSharper 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. If the output displays a link to a file that does not belong to the solution, you can click this link to open the file in an external application associated with the corresponding file type or Ctrl-click to open it in Visual Studio.

If you want to inspect specific stack trace later, press Ctrl+Shift+Alt+E or click Show Stack Trace in a new window Themed icon stack trace explorer tool window screen gray on the toolbar to open the stack trace in a new tab of the Stack Trace Explorer window.

By default, ReSharper 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 Tools | Unit Testing page of ReSharper options .

Use the Group by selector on the toolbar to change grouping of the tests — you can either choose one of the predefined grouping modes in the upper part of the selector, such as Test Hierarchy, Project Structure, and so on, or use the lower part of the selector to choose a custom set of grouping properties.

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

Unit test filters

By default, tests in all states are shown, but you can click the corresponding icons to filter tests by their state. You can also Ctrl-click several icons to display tests in several different states.

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

Themed icon running test screen gray

Unit test is currently executing

Themed icon test pending screen gray

Unit test is scheduled for execution in the current run

Themed icon status unknown screen gray

Unit test was not executed

Themed icon success screen gray

Unit test passed in the lats test run

Themed icon error screen gray

Unit test failed in the lats test run

Themed icon ignore screen gray

Unit test was ignored in the last test run

Either it has the corresponding attribute (for example Ignore for NUnit tests) or it is included in a category that is ignored in ReSharper settings.

Themed icon status aborted screen gray

Unit test was aborted in the last test run

Themed icon status inconclusive screen gray

Unit test was started but ReSharper could not read the test runner output. This normally happens when you abort test execution, but could also 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 Themed icon unit session 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.

Customize execution process

By default, ReSharper uses unit test project settings to define which .NET Framework version and processor architecture should be used when executing tests.

note

If execution settings are different in different unit test sessions, it is possible that a test passes in one session and fails in another. Therefore, ReSharper does not update execution results in other sessions, where the same tests are added. Also, the execution status icon displayed for a test in the editor corresponds to the result from the test session where it was last executed.

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 Tools | Unit Testing page of ReSharper options (Alt+R, O). 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 Options selector on the toolbar.

Study execution log

Unit Test Sessions 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.

If you have errors reported either by the test runner or ReSharper, the number of errors is displayed on the right side of the window's status bar, else OK is shown.

To display or hide the execution log, click the Log Themed icon session log screen gray button.

By default, only events with the 'Error' severity level are logged. If necessary, you can change the minimum severity level. To do so, either right-click the log area and choose the desired severity level or use the Show log entries... selector on the Tools | Unit Testing page of ReSharper options (Alt+R, O).

You can also copy the whole log to the clipboard by choosing the corresponding command in the context menu.