Run and debug Unity tests

warning

Rider requires the Unity project to have Test Framework 1.1.1 or later (can be installed with Unity Package Manager). If you want to analyze coverage of Unity tests, see the additional package requirements.

To work with Unity tests, use the Unit Tests window:

• Unity tests are discovered from code and from the Unity editor and are automatically added to the Explorer tab of the Unit Tests window.

• All Rider unit test features are available for Unity tests too including grouping, filtering based on test status, and other. Test output is parsed to make stack traces, class and method names into hyperlinks.

• You can add new Unity tests either in the Unity editor or in Rider. Unit test classes can be added via the Solution Explorer: in the context menu, select Add and then Play Mode Test or Edit Mode Test.

• The Unit Tests window allows you to choose which unit test runner you want to use. For example, it could be:

  • Standalone NUnit Launcher: NUnit test runner.

  • Unity Editor - Edit Mode: unit test runner embedded in Unity for running edit-mode tests.

  • Unity Editor - Play Mode: unit test runner embedded in Unity for running play-mode tests.

    warning

    Running play-mode tests from Rider requires Unity 2019.2 or later.

• You can run and debug edit-mode Unity tests as you run regular unit tests.

  

• Continuous testing is also supported for Unity tests.