JetBrains Rider
 
2023.1
Shortcuts: Visual Studio 2022 (Windows)
Get JetBrains Rider
You are viewing the documentation for an earlier version of JetBrains Rider.
  1. Run, debug, test, deploy
  2. Coverage analysis of .NET code
  3. Use Continuous Testing

dotUltimate or All Products Pack
Use Continuous Testing

Last modified: 20 March 2023

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

  1. Press Ctrl+Alt+S or choose File | Settings (Windows and Linux) or JetBrains Rider | Preferences (macOS) from the menu , then choose Build, Execution, Deployment | Unit Testing | Continuous Testing on the left.

  2. Specify when you need to rerun tests: after saving the solution, after building it, or after applying a shortcut (not assigned by default).

    JetBrains Rider: Continuous Testing settings

  3. 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 Unit Test Explorer window to create one.

  4. In the opened session tab, select a continuous testing mode for your session. 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 Outdated Tests. Learn more about continuous testing modes.

    note

    Outdated tests are tests that were affected by code changes.

  5. Coverage results will be shown in a separate Unit Tests Coverage window.

  6. That's it! You can start working as usual: change code, build or save (as needed), and see test results in real time.