Unit Testing Assistance in C++
ReSharper helps discover, run, and debug unit tests of Google C++ Testing Framework, C++ test framework, Catch, Boost.Test framework (v. 1.59 and above), and doctest unit testing framework right in Visual Studio.
With ReSharper, you can execute a single unit test, all tests in a file, project or solution. You can also execute any number of tests combined in a test session.
Discovering tests in the current document
ReSharper discovers unit tests right in the editor and adds the corresponding action indicators next to each item in the editor:
- a unit test that you can run or debug 
— the unit test passed during the last execution. 
— the unit test failed during the last execution.
Executing tests in the current document
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 and press Alt+Enter. In the action list, choose Run / Debug for a test class.
-
Alternatively, you can use the Run Unit Tests / Debug Unit Tests commands, which are available in the main menu ( ), in the context menu, or with Ctrl+T,R / Ctrl+T,D shortcuts correspondingly. These commands work differently depending on the caret position or selection in the editor:
To run or debug a single test, set the caret at the test name, or anywhere inside its declaration in the editor.
To run several tests, select the desired tests in the editor.
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 in this 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 choosing in the menu.
Discovering 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 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, and so on.
Navigate to source code of any test by double-clicking it in the view.
run or debug selected tests.
Create unit tests sessions from selected tests and/or add selected items to the current test session.
Export all tests from solution to a text, XML, or HTML file.
Executing 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, 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 
on the toolbar or use the corresponding shortcuts (Ctrl+T,R / Ctrl+T,D ). To run or debug tests from Solution Explorer or Class View, select one or more items ( files, folders, projects) that contain tests, and use the Run Unit Tests / Debug Unit Tests commands, which are available in the main menu ( ), in the context menu, or with Ctrl+T,R / Ctrl+T,D shortcuts correspondingly.
To run or debug all tests in solution, choose in 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 in this 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 choosing in the menu.
Using unit test sessions
ReSharper allows you to group unit tests that target specific part of your application into unit test sessions. A unit test session can contain tests from different projects. You can have multiple test sessions and run them separately as needed. A single test can be included into several different test sessions.
For detailed instructions related to unit test sessions, see Using Unit Test Sessions.
Execution process
ReSharper provides several ways to execute unit tests. Whichever way you choose, execution progress, test results, and output are displayed in the Unit Test Sessions window, coverage results are shown in the Unit Test Coverage window.
As tests are running in a unit test session, the execution progress is shown in the status bar under the toolbar of the Unit Test Sessions window and the Stop Execution 
button becomes active. You can click this button to abort execution of the tests. You can run multiple unit test sessions simultaneously. However, when you debug tests, only one test session can be executed at a time.
If necessary, you can enable the Track Running Test 
option on the toolbar. If it is on, the selection in the test tree switches automatically to the test that is currently running and the output panel always shows output of the current test during the execution.
You can also enable the Auto Scroll Output When Running Test 
option to follow output of tests as they are running.
When you run or debug unit tests, ReSharper uses the Command and Working Directory configuration parameters specified in the project properties. To access these properties, right-click the project and choose .
The Command Arguments property () is not used by default. To use it in test execution, select the corresponding checkbox on the page of ReSharper options (Alt+R,,O).
If execution settings are not specified in project properties (for example, in a library project, in an 'Open Folder' or CMake project), you can define them in the page of ReSharper options.
Analysing execution results and output
When the execution is over, the results are visualized in the Unit Test Sessions window.
The output pane (which you can place on the right or on the bottom using the Show Output 
button on the toolbar) displays output of the selected test.
By default, ReSharper wraps long lines in the output according to the current width of the output area. If necessary, you choose not to wrap long lines by clearing the Wrap long lines in Unit Test Session output checkbox on the page of ReSharper options.
On the status bar, you can see the total number of tests in the session as well as number of tests in different states: 
The same icons are used to display status of grouping items
The icons are also used on each session's tab to display the overall execution result of the sessions.
The corresponding icons above the test session tree show how many tests are in each of the states. The 
icon shows the total number of tests in the session.
Using these icons, you can filter the tree so that only tests in the corresponding status are displayed.
Configuring test runner
Unit test execution variables, such as command, its arguments, working directory, and environment variables are normally specified in project properties () and ReSharper will take them from there.
However, if these properties are not specified there (for example, in a library project, in an 'Open Folder' or CMake project), you can define execution settings on the page of ReSharper options (Alt+R,,O).
You can also use the Merge environment flag on that page. If it is selected, ReSharper will add environment variables specified in the Environment field to the environment variables from Visual Studio. If it is not selected, only environment variables from Visual Studio will be used.