Working with Unit Tests in Project or Solution
Discover unit tests in solution
ReSharper adds the Unit Test Explorer window to Visual Studio ( or , or Ctrl+Alt+T). Using this window, you can explore and run or debug unit tests of all supported frameworks in the entire solution. Note that unit tests from a project only appear in the window after the project is built. Tests from currently opened files are updated automatically, new tests from the opened files appear in the unit test explorer as soon as you create them.
In Unit Test Explorer, you can:
Explore tests in the solution: browse all unit tests in a tree view, search tests and filter by a substring, regroup unit tests by project, namespace, category, and so on.
Navigate to source code of any test or test class by double-clicking it in the view.
run or debug selected tests.
Create unit tests sessions from selected tests and test classs and/or add selected items to the current test session.
run or debug unit tests in project or solution
You can run or debug tests from the Unit Test Explorer , Solution Explorer, or Class View. Unit Test Explorer gives you the advantage to see only tests and test classes, while using other windows you need to know, which projects, files, and classes contain tests.
To execute tests from Unit Test Explorer, select the desired tests and click Run Unit Tests Ctrl+T R/ Debug Unit Tests Ctrl+T D on the toolbar.
To run or debug tests from Solution Explorer or Class View, select one or more items ( classes, files, folders, projects) that contain tests, and use the Run Unit Tests Ctrl+T R/ Debug Unit Tests Ctrl+T D commands, which are also available in the main menu ( ) and in the context menu.
To run or debug all tests in solution, choosein the main menu or press Ctrl+T L.
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+T T or choosingin the menu.