Skip to main content

Azure DevOps Integration

RoostGPT integrates with Azure DevOps for both source control and requirements management.

What's Supported

FeatureDetails
Git RepositoriesAzure Repos — create PRs with generated tests
Work ItemsPull user stories / requirements for test context
WebhooksTrigger test generation on push or PR events
Service HooksThree subscriptions needed: Code pushed, PR created, PR merged

Git Integration (Azure Repos)

Configure an Azure DevOps PAT with Code + Pull Request permissions.

See the Azure DevOps Git Configuration guide for token generation and setup steps.


Work Item Integration (Requirements)

RoostGPT can fetch Azure DevOps work items (User Stories, Tasks, Features) and use them as AI context during test generation.

Configuration

  1. Click Connectors in the top navigation bar → Thirdparty Apps
  2. Select Azure DevOps
  3. Enter:
    • Org URL: https://dev.azure.com/your-organization
    • PAT Token: A token with Work Items (Read) scope

During Test Creation

  • Set Business Requirement Source to Azure DevOps
  • Enter the Work Item ID
  • RoostGPT fetches the work item title, description, and acceptance criteria

CLI

ADO_ORG_URL=https://dev.azure.com/your-organization
ADO_PAT_TOKEN=your_pat_token
ADO_WORK_ITEM_ID=12345

Webhook Setup

Azure DevOps uses Service Hooks instead of standard webhooks. You need to create three separate subscriptions.

See the Webhooks guide — Azure DevOps section for step-by-step screenshot instructions.

Summary:

  • Navigate to Project Settings → Service Hooks → Create Subscription → Web Hooks
  • Create subscriptions for: Code pushed, Pull request created, Pull request merged
  • Use webhook URL: https://<your-roost-domain>/api/application/client/git/events/add

Test Output

When RoostGPT generates tests with Azure Repos as the target:

  1. Tests are committed to a new branch in your Azure repository
  2. A Pull Request is automatically created targeting your configured base branch
  3. The PR link is displayed in the RoostGPT UI and optionally sent via notification
  4. Your team reviews and merges the PR as normal