Connect Azure Boards to Test Companion
Connect Azure Boards to Test Companion to use work item context directly in chat for generating test cases and automation scripts.
Your Azure Boards work items already contain the acceptance criteria, edge cases, and issue details you need to test. When you connect Azure Boards to Test Companion, you can paste a work item link in chat and Test Companion automatically pulls in the ticket context, eliminating the need to copy details manually.
This integration helps you generate test cases and automate processes more quickly while staying inside your Test Companion.
After you connect Azure Boards, you can:
- Generate test cases from any work item: by pasting the Azure Boards link in chat. User Stories, Bugs, Features, and any other work item type are supported.
- Turn work-item-driven scenarios into automation code: by asking for scripts in your framework.
Test Companion can only fetch work items that your Azure DevOps account can access. Your Azure DevOps permissions still apply when Test Companion reads work item context.
Prerequisites
Before you start, confirm the following:
- You have installed Test Companion in your IDE and are signed in.
- You have completed the Azure DevOps integration flow to connect your Azure DevOps account.
- 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.
- Go to BrowserStack Integrations.
- Find Azure Test Plans in the list of available Test Management Tools integration.
- 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:
- Open Test Companion in your IDE.
-
Paste one or more Azure Boards work item links in the chat message.

- Add what you want Test Companion to do with those work items. For example:
Generate test cases for this user storyWrite Playwright automation for the scenarios in this bugWhat edge cases should I test based on this feature?
- Click Send message (➤).
Test Companion pulls the ticket context and generates results based on the work item details.
If the task is interrupted because Azure DevOps was not connected yet, complete the integration flow and then repeat the same prompt.
Auto-link requirements to generated test cases
When you share a requirement work item, such as a User Story or Feature, and generate test cases from it, Test Companion automatically populates the Requirement field in Test Management with the link to that work item. This provides traceability from the requirement to the test case without any additional steps.
What Test Companion reads from Azure Boards
Test Companion fetches the following fields from your work item:
| Field | Description |
|---|---|
| Work Item ID | The unique identifier (e.g., #1234) |
| Title | The work item title |
| Description | The full description and acceptance criteria |
Supported process types
Azure Boards supports multiple process types, including Agile, Scrum, Basic, and CMMI. Test Companion is compatible with all of them. No matter whether your project tracks User Stories (Agile), Product Backlog Items (Scrum), Issues (Basic), or Requirements (CMMI), you can paste the link, and Test Companion will understand the context.
Known limitations
- Read-only access. Test Companion reads work item context from Azure Boards. It does not create, edit, or update work items in Azure DevOps.
- Custom fields are not supported yet. Only the standard fields (ID, Title, Description) are fetched. Custom fields from Azure Boards work items are not currently read by Test Companion, so any information stored in custom fields will not be included in the context for test generation or automation. We recommend including all relevant details in the description field to ensure Test Companion has the necessary information to work with.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!