Use Continuous Testing
The concept of continuous testing implies that you have actual test results instantly, as soon as you've changed your code. Thus, there's no need to manually rebuild the project and re-run all tests after making changes: the impacted tests are run in the background automatically (the testing session is triggered by some explicit action, for example, saving changes or building the project).
Enable continuous testing in a solution
Press Ctrl+Alt+S or choose (Windows and Linux) or (macOS) from the menu , then choose on the left.
Configure Continuous Testing:
Specify how you want to trigger test runs: by saving the solution, building it, or applying a shortcut. To do this, select the corresponding option in Trigger Continuous Testing on.
Specify Continuous Testing Mode: For example, if you want JetBrains Rider to autorun tests and get coverage each time you save or build the solution or apply a shortcut, select Cover New and Affected Tests. Learn more about continuous testing modes.
Create a new unit testing session or open one that has the scope you want to cover by continuous testing. If you don't have any sessions yet, you can use the Tests window to create one.
In the session tab, enable continuous testing.
This will create a separate Continuous Testing Session.
If you don't have any coverage data, or it is outdated for tests in the scope, perform initial coverage analysis, e.g., with the Cover All Tests action.
That's it! You can start working as usual: change code, build or save (to trigger continuous testing), and see test results in real time.
Coverage results of the Continuous Testing Session will be shown in the Test Coverage window.
If coverage highlighting is enabled, you will see the coverage status of each code line right in the editor.
To quickly turn continuous testing on or off and see the test status, you can use the dotCover icon in the status bar.
