Working with unit tests in current document
Last modified: 21 July 2022tip
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:

... and in the File Structure window:

The method is a unit test and you can run and debug it. | |
The class is a unit test class and you can run and debug containing tests. | |
The unit test has passed during the last execution. | |
Tests in the unit test class have passed during the last execution. | |
The unit test has failed during the last execution. | |
At least one test in the unit test class has failed during the last execution. | |
The unit test was ignored during the last execution. | |
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 or debug unit tests in the current document. You can use action indicators, main menu or shortcuts:
To run or debug a single test or all tests in a test class, click the action indicator next to it or set the caret at the test /test class and press Alt+Enter. In the action list, choose Run/Debug for a test or Run All/Debug All for a test class.
Alternatively, you can use the Run Unit Tests
Ctrl+U R/ Debug Unit Tests
Ctrl+U D 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 or debug a single test or all tests in a test class, set 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.
To run several tests, select the desired tests in the editor or in the File Structure window.
To run all tests in the current file, either select all or set the caret outside test classes.
Whatever way you choose to run or debug 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 Ctrl+U U or choosing ReSharper | Unit Tests | Repeat Previous Run in the menu.