Integrations with external systems

Integration is an Allure TestOps entity that enables interaction with external systems, such as CI servers, issue/task trackers, third-party TMSs. Each integration is specific to a certain service.

Allure TestOps ecosystem diagram

Basic steps to configure an integration:

In the external service, install a plugin that adds Allure TestOps support. This step is optional and depends on the service.
In the global settings in Allure TestOps, specify the external service URL.
In the project settings in Allure TestOps, enter the credentials and change related settings, e.g., create a new job.

Most integrations require an exchange of authentication tokens between Allure TestOps and the external service. This allows both sides to request the necessary data from each other or trigger certain actions. You can find the instructions on how to generate and use these tokens on the specific integration page.

Integration with CI servers

Name	Connection check	Pipeline list	Pipeline runs	Job synchronization
Azure DevOps	✅	✅	✅	✅
AWS Code/Pipelines	✅	✅	✅	✅
Bamboo	✅	✅	✅	✅
Bitbucket	✅	✅	✅	✅
CircleCI	✅	✅	✅	✅
GitHub	✅	❌	✅	✅
GitLab	✅	✅	✅	✅
Jenkins	✅	✅	✅	✅
Tekton	✅	✅	✅	✅
TeamCity	✅	✅	✅	✅

Integration with issue trackers

Name	Connection check	Issue creation	Issue list	Launch export	Test case export
Azure DevOps	✅	✅	✅	✅	❌
BitBucket	✅	❌	✅	✅	❌
GitLab	✅	✅	✅	✅	❌
Jira Server (DC)	✅	✅	✅	✅	✅
Jira Cloud	✅	✅	✅	✅	✅
RedMine	✅	✅	✅	❌	❌
Targetprocess	✅	✅	✅	✅	❌
YouTrack	✅	✅	✅	✅	❌
Wrike	✅	✅	✅	✅	❌
Yandex Tracker	✅	✅	✅	✅	❌

Integration with third-party TMSs

Name	Connection check	Test case linking	Test case creation	Launch export
Azure DevOps	✅	❌	❌	✅
TestRail	✅	✅	✅	✅
Allure TestOps	✅	✅	✅	✅
Zephyr Scale/TM4J (Jira Server/DC)	✅	✅	✅	✅
Zephyr Scale Cloud (for Jira cloud)	✅	✅	✅	✅
XRay (for Jira Server/DC)	✅	✅	✅	✅
XRay Cloud (for Jira Cloud)	✅	✅	✅	✅