[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
  System Requirements
  Improve Performance
 [Expand]Features by Language
 [Expand]Getting Started
 [Expand]How To
 [Expand]Coding Assistance
 [Expand]Navigation and Search Tools
 [Expand]Static Code Analysis
 [Expand]Visualization Tools
 [Expand]Code Style Assistance
  Building Assistance
  Debugging Assistance
 [Expand]Refactoring Assistance
 [Collapse]Unit Testing Assistance
   Testing Framework Configuration
   Running and Debugging Tests
   Test Execution Output
   Working with Test Sessions
   Code Coverage Calculation
   JavaScript Test Runner
   Unit Test Builder
 [Expand]Decompiling Tools
 [Expand]Configuration Options
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)

Working with Test Sessions

The Unit Test Runner supports sessions. This enables you to create several test sets and run them independently. There are two ways to create a session.

Expanded Creating a New Session

From the Code Editor

Click the icon that supplements the Test or TestFixture attribute and select the Add to session | Create a new session menu item.

From the Test Runner Window

Right-click a node in the Test Runner window and select the Add to session | Create a new session menu item.

After the session is created, you can name it by renaming the newly added Test Runner window tab. Double click the tab text to edit it.

The tests included in the session are defined by one or more filters (e.g., namespace, type, assembly, etc.). You can extend any session with a set of tests: follow the procedure of creating a new session, but choose the required session (instead of creating a new one) at the final step. Session tests update automatically as you create new tests that match the session's filter.


Sessions are saved to the solution's .suo file and will persist after the Visual Studio restart.

Is this topic helpful?​​​​​​​