Visual Studio Test Controller component directory
The tables on this page list the IDs that you can use to install Visual Studio from the command line, or that you can specify as a dependency in a VSIX manifest. We'll add additional components when we release updates to Visual Studio.
Also note the following about the page:
- Each workload has its own section, followed by the workload ID and a table of the components that are available for the workload.
- By default, the Required components will be installed when you install the workload.
- If you choose to, you can also install the Recommended and Optional components.
- We've also added a section that lists the additional components that are not affiliated with any workload.
When you set dependencies in your VSIX manifest, you must specify Component IDs only. Use the tables on this page to determine the minimum component dependencies. In some scenarios, this might mean that you specify only one component from a workload. In other scenarios, it might mean that you specify multiple components from a single workload or multiple components from multiple workloads. For more information, see the How to: Migrate extensibility projects to Visual Studio page.
For more information about how to use these IDs, see the Use command-line parameters to install Visual Studio page. For a list of workload and component IDs for other products, see the Visual Studio workload and component IDs page. Lastly, refer to the Visual Studio out-of-support components page for a listing of those components that have transitioned to an out-of-support state and are now considered insecure. We recommend that you remove them during your next update.
To install these components by using the manual installer, download and run the Test Controller for Visual Studio.
Test Controller
ID: Microsoft.VisualStudio.Workload.TestController
Description: Distribute automated tests to multiple machines
Components included by this workload
| Component ID | Name | Version | Dependency type |
|---|---|---|---|
| Microsoft.VisualStudio.ComponentGroup.TestTools.TestController | Test Controller core features | 16.0.28315.86 | Required |
Unaffiliated components
These are components that are not included with any workload, but may be selected as an individual component.
| Component ID | Name | Version |
|---|---|---|
| n/a | n/a | n/a |
When you set dependencies in your VSIX manifest, you must specify Component IDs only. Use the tables on this page to determine the minimum component dependencies. In some scenarios, this might mean that you specify only one component from a workload. In other scenarios, it might mean that you specify multiple components from a single workload or multiple components from multiple workloads. For more information, see the How to: Migrate extensibility projects to Visual Studio page.
For more information about how to use these IDs, see the Use command-line parameters to install Visual Studio page. For a list of workload and component IDs for other products, see the Visual Studio workload and component IDs page. Lastly, refer to the Visual Studio out-of-support components page for a listing of those components that have transitioned to an out-of-support state and are now considered insecure. We recommend that you remove them during your next update.
To install these components by using the manual installer, download and run the Test Controller for Visual Studio.
Test Controller
ID: Microsoft.VisualStudio.Workload.TestController
Description: Distribute automated tests to multiple machines
Components included by this workload
| Component ID | Name | Version | Dependency type |
|---|---|---|---|
| Microsoft.VisualStudio.ComponentGroup.TestTools.TestController | Test Controller core features | 17.12.35410.122 | Required |
Unaffiliated components
These are components that are not included with any workload, but may be selected as an individual component.
| Component ID | Name | Version |
|---|---|---|
| n/a | n/a | n/a |
Support or troubleshooting
Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.
Here are a few more support options:
- We offer an installation chat (English only) support option for installation-related issues.
- Report product issues to us via the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE. If you're an IT Administrator and don't have Visual Studio installed, you can submit IT Admin feedback here.
- Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.