> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/integrations/azure-devops.md). # Azure DevOps Connect Azure DevOps to ContextQA, generate tests from Azure Boards work items, report failed runs as bugs, and link execution evidence. ## Quick answer Connect Azure DevOps under **Integrations & Plugins**. You can then use **Assets → Requirements → New Requirement → Generate from Integrations** to select Azure Boards work items for AI test generation, or select **Bug** on a failed run and choose Azure DevOps as the defect destination. ContextQA keeps a link between the work item and the requirement or run evidence. ## What this page covers {% hint style="info" %} **Who is this for?** SDETs, developers, and engineering managers who use Azure Boards for issue tracking and want to push test failures directly as work items. {% endhint %} The ContextQA Azure DevOps integration supports two user-facing loops: * **Requirement to coverage** — select Azure Boards work items and let ContextQA generate reviewable tests from their content. * **Failure to defect** — create a work item from a failed run with reproduction context and a link back to the evidence. ![ContextQA integrations catalog showing Jira, Slack, Linear, Azure DevOps, GitHub, Figma, test lab, and CI/CD options](https://4255556216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKlyaXxb76z3Dn47TrZkU%2Fuploads%2Fgit-blob-6e18cb614b0b6261dc6b81bbf95a26dc6d629988%2Fcontextqa-integrations-catalog.png?alt=media) *** ## Setting up the Azure DevOps integration ### Step 1: Generate a Personal Access Token in Azure DevOps 1. Open your Azure DevOps dashboard. 2. Go to your profile menu, select the three-dot menu, and choose **User settings**. 3. Select **Profile**, then navigate to **Personal access tokens**. 4. Click **New token**. 5. Give the token a clear name and grant the narrowest Azure Boards work-item permissions the ContextQA workflow requires. Avoid **Full access** unless your administrator and ContextQA support confirm that it is necessary. 6. Click **Create** and copy the generated token immediately. You will not be able to view it again after closing the dialog. ### Step 2: Enable the Azure DevOps plugin in ContextQA 1. In ContextQA, click **Settings** in the left sidebar. 2. Open **Integrations & Plugins**. 3. Find **Azure DevOps Board** in the plugin list and enable it. ### Step 3: Enter your integration credentials 1. Paste the Personal Access Token copied in Step 1 into the access key field. 2. Enter your Azure DevOps organization URL (copy this from the address bar of your Azure DevOps portal, for example `https://dev.azure.com/your-org`). 3. Click **Create**. ContextQA verifies the credentials and confirms a successful connection. The integration is now active for all projects in your ContextQA workspace. *** ## Generate tests from Azure Boards work items 1. Open **Assets → Requirements** and select **New Requirement**. 2. Choose **Generate from Integrations**. During a staged rollout, the first card may still read **Generate from Jira** before the integration chooser appears. 3. Choose **Azure DevOps**. If it is not connected, follow the link back to **Integrations & Plugins**. 4. Search by work-item ID or title. Narrow the list by **Project** and **Work Item Type** when needed. 5. Select the work items and click **Continue**. 6. Choose the platform, publish mode, environment, test-case types, and optional context. 7. Start analysis. Answer clarification questions when ContextQA needs more information. 8. Open the resulting requirement and review **Test Cases**, **Questionnaire**, **Requirement Data**, **Metadata**, and **Gaps** before approval. The picker supports multiple selections and reports unreadable items before generation. Remove failed items rather than publishing a partial selection accidentally. ```mermaid flowchart LR A[Azure Boards work items] --> B[Integration picker] B --> C[AI analysis and clarifications] C --> D[Requirement record] D --> E[Reviewable test cases] E --> F[Test repository and execution] ``` *** ## Creating work items from test failures Once the integration is configured, you can report a bug to Azure Boards directly from any failing test result. ### Step 1: Identify a failed test case Open the execution result page for a failed test run. The failed step is highlighted with a red status badge, a screenshot, and an error message. ### Step 2: Start reporting a bug Click **Bug** in the test result toolbar. ### Step 3: Select Azure DevOps as the destination When the destination chooser opens, select **Azure DevOps**. The same action can also offer Jira when both integrations are configured. ### Step 4: Fill in work item details * **Issue type** — select the work item type appropriate for your Azure project (e.g., Bug, Test Case, Shared Step) * **Title** — enter a clear title; ContextQA automatically pre-fills the test description and reproduction steps in the description field to save time ### Step 5: Save and sync Click **Save**. The work item is created immediately in Azure Boards and a direct link appears in the ContextQA result page. ### Step 6: Verify in Azure Boards Follow the generated link to open Azure Boards and confirm the ticket was created. The work item includes the full bug description, test step history, and all context provided by ContextQA. *** ## Managing the work item in Azure Boards Once the ticket is in Azure Boards: * Assign it to the responsible developer using the standard Azure Boards assignment workflow * Use Azure Boards sprint and backlog management to prioritize the fix * Update the ticket status as the fix progresses — the link in ContextQA continues pointing to the same ticket so QA engineers can monitor resolution *** ## Configuring project and area path When creating work items, ContextQA uses the organization and credentials provided during setup. If your Azure DevOps organization contains multiple projects, select the appropriate project in the work item creation dialog each time you report a bug. Azure Boards manages area path and iteration configuration according to your existing project structure. *** ## Azure Pipelines CI/CD integration Use an Azure Pipelines stage to coordinate a ContextQA test-plan run and require its result before deployment. Before configuring the stage: 1. Create and manually validate the test plan. 2. Open its **CI / CD** tab and confirm Azure DevOps is listed. 3. Obtain the current public start and status contract supplied for your workspace. 4. Create a dedicated [API token](/administration/api-tokens.md) with the narrowest required scopes. {% hint style="warning" %} The verified production **CI / CD** tab describes start and status operations but does not display public endpoint paths. Do not use older account-password or `/testplans/{id}/execute` examples, and do not copy internal URLs from portal network traffic. {% endhint %} In **Pipelines → Library → Variable Groups**, add the API token as a secret variable named `CONTEXTQA_API_TOKEN`. Store the test plan ID and the public base URL, when supplied, as non-secret variables. Authorize the variable group only for the pipelines that need it. When the public contract is available, the stage should: 1. Start the plan with the published method, path, and payload. 2. Capture the returned run ID. 3. Poll the published status operation with a bounded timeout. 4. Return a non-zero exit code for every documented non-success result. 5. Include the run ID in the job output so reviewers can find the run in ContextQA. Place the stage after the target environment is ready and before the protected deployment stage. Use environment approvals and checks when production requires an additional human gate. *** ## Traceability With both the Jira and Azure DevOps integrations in use, ContextQA can push bugs to whichever tracker your team uses. Each bug includes: * A link to the ContextQA result page with screenshots, video, and step logs * The reproduction steps generated by the AI * The test case name and ID for lookup in ContextQA * A direct execution or result link when the work item was created from an external Azure DevOps workflow This gives developers enough context to begin triage from Azure Boards. Opening the linked screenshots, video, logs, or live result still requires authorized access to the corresponding ContextQA organization and workspace. ## Related documentation * [Requirements management](/web-testing/requirements-management.md) * [Execution and test results](/reporting/test-results.md) * [PR Impact Analysis](/ai-features/pr-impact-analysis.md) * [API tokens](/administration/api-tokens.md) {% hint style="info" %} **Connect ContextQA to your CI/CD pipeline in 15 minutes.** [**Book a Demo →**](https://contextqa.com/book-a-demo/) — See the full integration walkthrough for your existing toolchain. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://learning.contextqa.com/integrations/azure-devops.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.