Connect Azure Boards to Test Companion

In Visual Studio Code, Test Companion finds, reads, creates, and updates work items through the Azure DevOps MCP server. You name the work item in chat. Test Companion asks for your approval before it fetches the work item.

Prerequisites for the MCP server

Ensure you have the following:

• Test Companion is installed in Visual Studio Code and you are signed in.
• A Microsoft account with access to the Azure DevOps projects you want to use.
• An Azure administrator has completed the one-time setup for your Microsoft Entra tenant. Until then, the Microsoft sign-in fails for everyone in your organization. The steps are in One-time setup by an Azure administrator.

Connect the Azure DevOps MCP server

To connect the server:

1. Click ... (more options) on the Test Companion panel, then select MCP Servers.

2. Select the Catalog tab, then click Connect on the Azure DevOps card.

   

3. Sign in with your Microsoft account in the browser and grant the requested access, then return to your IDE. The Installed tab shows the server with a green dot and its tool count.

For the controls of a connected server, see Azure DevOps in Connect an MCP server to Test Companion.

Use Azure Boards work items in chat

To work with a work item:

1. Describe the task and name the work item by its ID. For example: Get user story 4812 from Azure Boards and generate test cases for its acceptance criteria.
2. When the approval card appears, click Approve.

Test Companion reads the work item and continues the task. It can also create and update work items when you ask. Each change shows an approval card first.

You can also paste a work item link in chat. A pasted link uses the BrowserStack integration described in the Other IDEs tab, not the MCP server.

In JetBrains IDEs, Visual Studio, and Eclipse, Test Companion reads work items through the BrowserStack integration. You paste a work item link in chat. This route also works in Visual Studio Code.

Prerequisites for the integration

Ensure you have the following:

• Test Companion is installed in your IDE and you are signed in.
• Your Azure DevOps account is connected through the Azure DevOps integration flow.
• You can open the Azure Boards work item in your browser.

Connect your Azure DevOps account

You only need to complete this step once for your organization:

1. Go to BrowserStack Integrations.
2. Find Azure Test Plans in the list of available Test Management Tools integration.
3. Click Connect and authorize BrowserStack to access your Azure DevOps organization.

After you connect Azure DevOps, Test Companion can read work items from any project in your Azure DevOps organization.

Use Azure Boards work item links in Test Companion chat

Test Companion reads the work item ID, title, and description from the linked work item(s) and uses them as context for your request.

After you connect Azure DevOps, use Azure Boards links directly in the Test Companion chat:

1. Open Test Companion in your IDE.

2. Paste one or more Azure Boards work item links in the chat message.

   

3. Add what you want Test Companion to do with those work items. For example:
   • Generate test cases for this user story
   • Write Playwright automation for the scenarios in this bug
   • What edge cases should I test based on this feature?
4. Click Send message.

Test Companion pulls the ticket context and generates results based on the work item details.

What Test Companion reads from Azure Boards

Test Companion fetches the following fields from your work item:

Known limitations

The BrowserStack integration has the following limitations:

• Test Companion reads work item context from Azure Boards. It does not create, edit, or update work items in Azure DevOps.
• Test Companion reads only the ID, Title, and Description fields. Information in custom fields is not part of the context for test generation or automation. Put every relevant detail in the description field.