Working with Unit Tests in Current Document
Discovering Tests in the current document
JetBrains Rider discovers unit test classes and single unit tests of all supported frameworks right in the editor and adds the corresponding action indicators next to each item in the editor:
- the method is a unit test and you can run and debug it.
- the class is a unit test class and you can run and debug containing tests.
- the unit test passed during the last execution.
- tests in the unit test class passed during the last execution.
- the unit test failed during the last execution.
- at least one test in the unit test class failed during the last execution.
- the unit test was ignored during the last execution.
- all tests in the unit test class were ignored during the last execution.
Executing and covering tests in the current document
There are several ways to run, debug or cover unit tests in the current document. You can use action indicators, main menu or shortcuts:
To run, debug or cover a single test or all tests in a test class, click on the action indicator next to it or set the caret on the test/test class and press Alt+Enter. In the action list, choose Run / Debug or Cover for a test or Run All /Debug All or Cover All for a test class.
- Alternatively, you can 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+U, R / Ctrl+U, D shortcuts correspondingly. These commands work differently depending on the caret position or selection in the editor:
To run, debug or cover a single test or all tests in a test class, set the caret at the test/test class name, or anywhere inside its declaration in the editor.
To run several tests, select the desired tests in the editor.
To run all tests in the current file, either select all or set the caret outside test classes.
Whatever way you choose to run, debug or cover tests, you will see the execution progress, results, and output in the Unit Tests 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.