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.
You can group unit tests that target specific parts of your application into multiple unit test sessions. A unit test session can contain tests of different supported frameworks, from different projects. You can have multiple test sessions and run them separately as needed. A single test /test class can be included into several different test sessions.
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.
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.
All existing unit test sessions are displayed in tabs of the Unit Test Sessions window, where you can execute tests and analyze results.
The Unit Test Sessions window also visualizes the test runner activity: it displays execution progress as well as status and output of the executed tests. Each time you run or debug tests they are either added to the current test session or a new unit test session is created for them.
To search tests, start typing a test name or its CamelHumps abbreviation as soon as your focus is in this window.
Create and close unit test sessions
There are several ways to create a new test session:
Just run or debug unit tests from the current document or from the project/solution. 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.
In the editor, click an action indicator next to a test or test class or set the caret at this item and press Alt+Enter, and then choose Create New Session in the action list. A new session with this test/test class will be created.
In the Unit Test Explorer window, select tests/test classes for the new session and choose Create New Session from the context menu or press Control+T N.
In the main menu, choose ReSharper | Unit Tests | Create New Session or press Control+T N. If the focus is in the editor or in the Unit Test Explorer window and some tests/test classes are selected, or the caret is at or inside a test/test class, the new test session is created with the corresponding items. Otherwise, an empty test session is created.
If you want to prevent adding new tests to the session, you can lock this session.
To close a unit test session, close the corresponding tab in the Unit Test Sessions window. The closed session will not be available anymore.
Add and remove items in a test session
By default, if you run or debug tests that are not included into any session the tests are added to the current session.
If you want to prevent adding new tests to the session, you can lock this session.
There are other ways to add tests/test classes to a session:
In the editor, click an action indicator next to a test or test class or set the caret at this item and press Alt+Enter, and then choose Append to [current session] in the action list. If you want to add the item to another section, click the small arrow next to this command and choose any of the existing test sessions in a sub-menu:
You can also choose ReSharper | Unit Tests | Append Tests to Session in the main menu or press Control+T A to add the selected items to a session.
In the Unit Test Explorer window, select tests/test classes that you want to add and click Append Tests to Session on the toolbar or press Control+T A. If there are more than one session, choose the target session in the popup that appears.
To remove tests from the session, select the tests or grouping items that you want to remove and click Remove Selected Tests on the toolbar.
Rename test sessions
By default, the first test/class that you add to a new test session is used as the session's name.
To rename a session, right-click the session's tab and choose Rename session from the context menu or double-click the tab, and then specify a new name for the session in the appeared dialog.
Lock and unlock unit tests sessions
By default, if you run or debug tests that are not included into any session the tests are added to the current session.
If necessary, you can prevent adding new tests to a session. To do so, in the Unit Test Sessions window switch to the tab of the session that you want to lock, click Options on the toolbar, and then select Lock Session.
To unlock the session, repeat the same actions.
Save and restore unit test sessions
By default, unit test sessions are saved automatically for each solution; ReSharper keeps them even if you close and reopen the solution. If necessary, you choose not to keep unit test sessions by clearing the Save and restore Unit Test Sessions checkbox on the Tools | Unit Testing page of ReSharper options.
If necessary, you can also save any test session in a file and then open it when needed. To save a session, select the corresponding tab in the Unit Test Sessions window and click Export Session on the toolbar and then choose where to save the session file.
To open a saved session, click Import Session in the Unit Test Explorer or Unit Test Sessions window and then select a .testsession file.
from the context menu or press Control+T N.
on the toolbar or press Control+T A. If there are more than one session, choose the target session in the popup that appears.
on the toolbar.
.
on the toolbar and then choose where to save the session file.
in the Unit Test Explorer or Unit Test Sessions window and then select a .testsession file.