Working with Unit Tests in Project or Solution
Discovering unit tests in solution
dotCover adds the Unit Test Explorer window to Visual Studio ( or , or Ctrl+Alt+T ). Using this window, you can explore and run, debug or cover 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.
Unit test explorer allows you to do the following:
Explore tests in the solution: browse all unit tests in a list or 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, debug or cover selected tests.
Create unit tests sessions from selected tests and test classs and/or add selected items to the current test session.
Export all tests from solution to a text, XML, or HTML file.
Executing and covering unit tests in project or solution
You can run, debug or cover 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 / Debug Unit Tests or Cover Unit Tests on the toolbar or use the corresponding shortcuts (Ctrl+T R / Ctrl+T D or Ctrl+T H ).
To run, debug or cover 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 / Debug Unit Tests or Cover Unit Tests commands, which are available in the main menu ( ), in the context menu, or with Ctrl+T R / Ctrl+T D or Ctrl+T H shortcuts correspondingly.
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 in this session. If there are no test sessions or the existing ones are locked, then a new tests session is created.