Ask the Community
Connect Azure Test Plans to Test Companion
Learn how to connect Azure Test Plans to Test Companion to bring your manual test cases into Test Companion without the need to copy and paste steps or expected results.
If your team manages manual test cases in Azure Test Plans, you can bring them into Test Companion without copying test steps, expected results, or configurations by hand.
When you connect Azure Test Plans, you can browse your test plans and suites in a folder view inside Test Companion, select test cases, and send them to Test Companion for automation. Test Companion reads the steps, expected results, and configurations directly from Azure Test Plans and uses them as context.
Test Companion can only fetch test cases that your Azure DevOps account can access. In other words, Azure DevOps permissions still apply when Test Companion reads test case data.
Prerequisites
Before you start, confirm these:
- Install Test Companion in your IDE and are signed in.
- Complete the Azure DevOps integration flow to connect your Azure DevOps account.
- Your test cases in Azure Test Plans belong to a test suite. Test cases that are not part of any suite cannot be accessed through this integration.
Connect your Azure DevOps account
You only need to complete this step once for your organization.
- Go to BrowserStack Integrations.
- Find Azure in the list of available integrations.
- 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.
Browse Azure Test Plans in Test Companion
After you connect, you can browse your Azure Test Plans hierarchy directly from the Test Cases tab.
- Click Test Cases icon (see annotation 1) to open the Test Cases tab in Test Companion.
-
In the Test Management Service dropdown, select Azure (see annotation 2).
-
In the Project dropdown, select the Azure DevOps project that contains your test plans. The dropdown loads available projects automatically and supports search.
-
Your test plans and suites appear in a folder view on the left panel. Click any suite to load its test cases in the grid on the right.
Static sub-suites appear as nested folders. All suite types are supported, including static, requirement-based, and query-based.
If the task was interrupted because Azure DevOps was not connected yet, repeat the same prompt after completing the Azure DevOps integration flow to connect your account.
Auto-link requirements to generated test cases
When you share a test case that has a linked work item (such as a User Story or Requirement) and generate test cases from it, Test Companion automatically populates the Requirement field in Test Management with the work item link. This gives you traceability from requirement to test case without any extra steps.
Select test cases for automation
After your test cases are loaded in the grid, select the one you want to automate and click the Automate button to send them to Test Companion. The automation workflow from this point is the same as automating an existing test — select test cases, choose the UI Test Generator agent, write a prompt, and send.
What Test Companion reads from Azure Test Plans
When you select test cases or paste a link in chat, Test Companion fetches the following fields to build context:
| Field | What it provides |
|---|---|
| Test Suite Name | The name of the suite to which the test case belongs |
| Test ID | A unique identifier for the test case |
| Test Name | The title or name of the test case |
| Steps and Expected Results | The manual steps that the script should follow, along with the expected outcomes |
| Shared Steps | Reusable sequences of steps that can be referenced across multiple test cases |
| Linked Work Item | The associated requirement or backlog item, if applicable |
| Configurations | Parameters including browser, operating system, and environment (in JSON format) |
| Automation Status | Indicates whether the test case has been marked as automated |
Known limitations
- Read-only access: Test Companion reads test cases from Azure Test Plans but does not create, modify, or delete test cases, suites, or plans in Azure DevOps.
- Suite membership required: Test cases that do not belong to any suite are not displayed. Move them to a suite in Azure DevOps to make them accessible.
- Shared parameters: Test Companion fetches shared parameters when available, but full resolution of shared parameters across configurations is planned for a future release.
Next steps
- Automate tests: Learn how to convert selected test cases into automation scripts.
- Generate test cases: Generate new test cases from requirements or by exploring a URL.
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!