ReSharper
 
2025.1
Shortcuts: Visual Studio
Get ReSharper
  1. Unit testing assistance
  2. In current document

Work with unit tests in current document

Last modified: 15 May 2024

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.

Discover tests in the current document

ReSharper discovers unit test classes and single unit tests of all supported frameworks right in the editor and adds the corresponding action indicators next to each item in the editor:

ReSharper shows different indicators for unit tests in the editor

... and in the File Structure window window:

ReSharper shows unit tests in File Structure

Test

The method is a unit test and you can run and debug it.

Test

The class is a unit test class and you can run and debug containing tests.

Passed

The unit test has passed during the last execution.

Passed

Tests in the unit test class have passed during the last execution.

Failed

The unit test has failed during the last execution.

Failed

At least one test in the unit test class has failed during the last execution.

Ignored

The unit test was ignored during the last execution.

Ignored

All tests in the unit test class were ignored during the last execution.

note

If a unit test is included in several unit test sessions, its execution status icon corresponds to the result from the test session where it was last executed.

Run, debug, or cover tests in the current document

note

Unit test coverage analysis requires dotCover to be installed and enabled. dotCover is available with the dotUltimate or All Products Pack license.

There are several ways to run, debug, or cover unit tests in the current document. You can use action indicators, main menu or shortcuts:

  • To run, debug, or cover a single test or all tests in a test class, click the action indicator next to it or place the caret at the test /test class and press AltEnter. In the action list, choose Run/Debug for a test or Run All/Debug All for a test class.

    ReSharper: Recognizing unit tests in the editor

  • Alternatively, you can use the Run Unit Tests Run Unit Tests Ctrl0U,0R/Debug Unit Tests Debug Unit Tests Ctrl0U,0D commands, which are also available in the main menu (ReSharper | Unit Tests) and in the context menu. These commands work differently depending on the caret position or selection in the editor:

    • To run, debug, or cover a single test or all tests in a test class, place the caret at the test /test class name, or anywhere inside its declaration in the editor , or else, select it in the File Structure window window .

    • To run several tests, select the desired tests in the editor or in the File Structure window window .

    • To run all tests in the current file, either select all or place the caret outside test classes.

Whatever way you choose to run, debug, or cover tests, you will see the execution progress, results, and output in the Unit Test Sessions window. If there is an open unit test session, the executed tests are added to that session. If there are no test sessions or the existing ones are locked, then a new tests session is created.

If necessary, you can always re-run the tests that you executed last by pressing Ctrl0U,0U or choosing ReSharper | Unit Tests | Repeat Previous Run from the menu.

Inlay hints for test data attributes

To help you understand how the arguments of test data attributes are used in test methods, ReSharper displays parameter name hints for the following attributes:

  • NUnit's TestCase attribute,

  • xUnit's InlineData attribute,

  • InlineAutoData attribute from AutoFixture.NUnit3 and AutoFixture.Xunit2.

ReSharper: Inlay hings for NUnit TestCase attribute

If you want to disable these inlay hints, use the corresponding checkboxes on the Environment | Inlay Hints | C# | Parameter Name Hints page of ReSharper options Alt+R, O