tldr: Tricentis Tosca integrates with Azure DevOps through the Tosca Execution Client (available on GitHub). You can trigger Tosca test executions from Azure Pipelines, sync test results to Azure Test Plans, and gate deployments based on test outcomes. Setup requires Tosca DEX (Distributed Execution).
How the integration works
The Tricentis Tosca Azure DevOps integration connects two systems:
- Azure Pipelines triggers Tosca test execution as a build or release step
- Tosca DEX (Distributed Execution) runs the tests on configured agents
- Results sync back to Azure DevOps for reporting and release gating
The integration uses the Tosca Execution Client, an open-source tool available on GitHub (github.com/Tricentis/ToscaExecutionClient). There is also a third-party bidirectional integration by OpsHub in the Azure DevOps Marketplace. You configure connection settings and add Tosca execution steps to your pipelines.
Setting up the integration
Prerequisites:
- Tricentis Tosca installed with DEX configured
- Azure DevOps organization with pipelines enabled
- Tosca CI/CD integration license (check with your Tricentis account manager)
- Network connectivity between Azure DevOps agents and Tosca server
Step 1: Set up Tosca Execution Client
Download the Tosca Execution Client from GitHub (github.com/Tricentis/ToscaExecutionClient). This is the bridge between Azure Pipelines and Tosca DEX. Configure it with your Tosca server details.
Step 2: Configure the connection
You'll need:
- Tosca server URL and Automation Object Service (AOS) endpoint
- Authentication credentials (username/password or token)
- Workspace name
- Execution list names for the tests you want to run
Step 3: Add Tosca execution to your pipeline
In your Azure Pipeline (YAML or classic editor), add a step that invokes the Tosca Execution Client. The client triggers DEX, waits for results, and returns pass/fail status to your pipeline.
Step 4: Map results to Azure Test Plans
Configure result mapping to sync Tosca test outcomes to Azure Test Plans. This gives you traceability from requirements to test cases to results within Azure DevOps.
What you can do with the integration
Trigger tests on every PR. Add a Tosca execution step to your PR validation pipeline. Tests run automatically when a developer opens or updates a pull request.
Gate releases. Configure release pipelines to wait for Tosca test results before deploying to production. If tests fail, the deployment stops.
Parallel execution. Tosca DEX can distribute tests across multiple agents. Configure agent pools in Tosca to match your execution requirements.
Result visibility. Test results appear in Azure DevOps alongside build results. Developers see pass/fail status without logging into Tosca Commander.
Work item linking. Link Tosca test cases to Azure DevOps work items (user stories, bugs) for traceability across your development lifecycle.
Common setup challenges
Network connectivity. Azure DevOps cloud agents need to reach your Tosca server. If Tosca runs on-premises behind a firewall, you'll need self-hosted Azure DevOps agents or a VPN/tunnel. This is the most common integration blocker.
License requirements. CI/CD integration may require additional Tosca licenses beyond the base platform. Confirm with your Tricentis account manager before planning the integration.
Agent configuration. Tosca execution agents need browsers, runtime dependencies, and Tosca client software installed. Each agent runs on Windows. Linux-based CI agents won't work for Tosca execution.
Execution timing. Large Tosca test suites can take hours. Pipeline timeouts and execution windows need to align. Consider running full regression suites on a schedule rather than every PR, and running a smaller smoke test suite on PRs.
Result mapping complexity. Mapping Tosca test cases to Azure Test Plans requires careful configuration. Test case IDs, execution list structure, and result format all need to align. Plan for iteration during initial setup.
Tosca + Azure DevOps vs. modern alternatives
The Tosca-Azure DevOps integration works, but it's complex to set up and maintain. Here's the contrast:
| Aspect | Tosca + Azure DevOps | Bug0 + GitHub Actions |
|---|---|---|
| Setup time | Days to weeks | ~10 minutes |
| Agent requirements | Windows agents with Tosca client | None (cloud infrastructure) |
| Network configuration | VPN/tunnel for on-prem Tosca | None (cloud-to-cloud) |
| Test creation | Separate tool (Tosca Commander) | Same platform |
| Self-healing | Vision AI (extra license) | Included |
| Maintenance | Module updates + pipeline config | AI-powered, automatic |
For teams already invested in Tosca, the Azure DevOps integration adds CI/CD automation to their existing test suite. For teams starting fresh or evaluating options, Bug0 integrates with CI/CD in minutes with no infrastructure requirements.
FAQs
Does Tricentis Tosca work with Azure DevOps?
Yes. Tricentis provides the Tosca Execution Client (open-source on GitHub) to integrate Tosca with Azure Pipelines. There is also a third-party extension by OpsHub in the Azure DevOps Marketplace for bidirectional sync. You can trigger tests, gate releases, and sync results to Azure Test Plans.
How long does the Tosca Azure DevOps integration take to set up?
Plan for 2-5 days for a basic integration. This includes setting up the Tosca Execution Client, configuring DEX agents, and testing the pipeline. Complex environments with on-premises Tosca and network restrictions can take longer.
Do I need additional Tosca licenses for Azure DevOps integration?
CI/CD integration may require Tosca DEX licenses for distributed execution. Confirm with your Tricentis account manager. The Azure DevOps extension itself is typically included, but execution agent licenses are separate.
Can I run Tosca tests on Linux-based Azure DevOps agents?
No. Tosca execution requires Windows-based agents with the Tosca client installed. If your Azure DevOps pipeline uses Linux agents, you'll need separate Windows agents for the Tosca execution step.
What's the alternative to Tosca for Azure DevOps testing?
Open-source tools like Playwright run natively on any Azure DevOps agent. For AI-powered testing, Bug0 integrates with CI/CD via GitHub Actions in about 10 minutes with zero infrastructure setup.