ReSharper 2024.2 Help

Analyze test results

Analyze execution results and output

When test 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 ThemedIcon.StackTraceExplorerToolWindow.Screen.(Gray).png 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:

ThemedIcon.RunningTest.Screen.(Gray).png

Unit test is currently executing

ThemedIcon.TestPending.Screen.(Gray).png

Unit test is scheduled for execution in the current run

ThemedIcon.StatusUnknown.Screen.(Gray).png

Unit test was not executed

ThemedIcon.Success.Screen.(Gray).png

Unit test passed in the lats test run

ThemedIcon.Error.Screen.(Gray).png

Unit test failed in the lats test run

ThemedIcon.Ignore.Screen.(Gray).png

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.

ThemedIcon.StatusAborted.Screen.(Gray).png

Unit test was aborted in the last test run

ThemedIcon.StatusInconclusive.Screen.(Gray).png

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 ThemedIcon.UnitSession.Screen.(Gray).png 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.

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 ThemedIcon.SessionLog.Screen.(Gray).png 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 Maximum severity of log entries selector on the Tools | Unit Testing | General 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.

Last modified: 17 October 2024