The integration between PractiTest and Azure DevOps allows users to report issues from PractiTest test runs directly to Azure, link issues from the Azure project to a test step In PractiTest, import Azure tickets as Requirements in PractiTest, and sync issues into PractiTest from the Azure project. Tickets’ names, descriptions, and states are synced when the integration is configured.
These are important points to know and to prepare up-front before setting up the integration:
- The configuration needs to be done by PractiTest’s Account Owner.
- To configure the integration, you need to create a long-term personal access token in Azure DevOps by following the steps on this page.
- The user that creates the token must have permission to create work items in the relevant project inside Azure DevOps.
- The token must have permission to read and write work items.
Table of Contents
- Account Integration Setting
- PractiTest Panel Settings
- Fail & Issue – Report Issues to Azure DevOps
- Link existing issue
- Import Requirements
- Synchronizing Issues
- Field Mapping
Account Integration Settings
- Start in PractiTest Account Settings, and select the Integrations tab. Then, click on ‘Create a new 2-way account integration’.
Then select ‘Azure Devops’ from the options menu and click on ‘Create a new Azure Devops integration’:
- Paste the personal token you have created from your Azure DevOps project in the indicated box, and fill in the Azure DevOps Organization in the indicated box. Then click on “Update and Get Projects”:
- Create a unique prefix for your project by clicking on:
- Enter a unique prefix for each of the integrated projects (between 1-4 characters), and click on ‘Update Projects Prefixes’.
- Create a project service hook for every project you want to integrate with PractiTest. In Azure, go to Project settings – service hooks, and create a new subscription. Then, select the ‘Work item updated’ item for the ‘Trigger on this type of event’ field, and click on next. Finally, paste the webhook you got from the PractiTest integration settings page, and click on finish.
Then select ‘Azure Devops’ from the options menu and click on ‘Create a new Azure Devops integration’:
6.Project Settings – For each of the PractiTest projects you want to integrate with your Azure instance, you need to activate the integration at the project level. In order to enable the integration, go to Project Settings, select the Integrations tab, and activate the issue integration support.
Then, select ‘Azure DevOps’ from the dropdown list, and click on ‘Update Issue integration’.
Configuring Azure DevOps Project and Work Item Types
In order to sync work items between Azure DevOps and PractiTest, you first need to define which Azure DevOps projects and work item types will be mapped to your PractiTest project.
To configure this:
- Go to Project Settings in PractiTest.
- Open the Integrations tab.
- Select Azure DevOps Integration.
In the Azure DevOps Project Info and Issue Types section, you can define:
- Azure DevOps Projects – Select the Azure DevOps project(s) you want to sync with your PractiTest project.
- Work Item Types – Choose which work item types (such as User Story, Bug, Task, etc.) will be mapped and synced with PractiTest entities.
This configuration determines which Azure DevOps work items can be imported, linked, or created from PractiTest during test execution or issue reporting.
PractiTest Panel Settings
The PractiTest panel in Azure DevOps is officially available and can be downloaded directly from the Azure DevOps Marketplace.
1. Install PractiTest Extension
- From the Azure DevOps Marketplace, click on ‘Get if free’ button to download the panel extension.
- After installation, a confirmation screen will appear when the extension is successfully activated.
2. Configure the Connection
- Go to Organization Settings → Extensions → PractiTest.
- Configure the following:
3. Configure Azure Layouts at the Process Level
- By default, the PractiTest panel is added to all work items layouts within each process.
- Azure admin users can customize this by:
- Selecting specific processes where the panel should appear.
- Defining which work item types (e.g., User Stories, Bugs) will include the panel and where it should be positioned in the form.
- Navigate to Organization Settings → Process to make adjustments.
Example: To adjust the panel in the User Story Layout within a process, go to the process settings. You can choose to reposition or remove the PractiTest panel if it is not needed for that process.
4. Final View
- Once configuration is complete, the PractiTest panel will be visible on all work items configured within Azure DevOps.
Viewing Covering Test Information
If the Azure DevOps work item is synced to a PractiTest requirement and covered by tests, you will have a link to the tests covering the requirement. You can view detailed information, including the test steps, last run date, last run status, and test author. Additionally, the Requirement Status Bar provides a visual representation of the statuses of all tests linked to the requirement, with each status represented by a distinct color and proportional segment size.
Creating a New Test with Steps
If your Azure DevOps project is integrated with PractiTest, you can now create a new test with steps directly from a User Story in Azure DevOps.
Clicking on the ‘Create Test with Steps’ button in the PractiTest panel will automatically generate a new test in PractiTest, including the test name, description, and AI-generated steps, linked to the Azure DevOps story.
Note: This feature uses the Smart Fox AI assistant, which must be enabled in your PractiTest account. Your account owner must accept the AI usage terms in order to activate this capability.
Fail & Issue – Report Issues to Azure DevOps
After the integration is configured, you can create issues directly to your Azure project from a test run in PractiTest, by using the Fail & Issue option.
- Go to the Test Sets & Runs tab and select a test set
- Choose an instance to run.
3. Click ‘Fail & Issue’ under the relevant step.
4. A modal window will open where you can define the issue details. In this window, you can configure the following:
- Azure DevOps Project – Select the project where the issue will be created.
- Entity Type – Choose the type of work item to create in Azure DevOps (for example, Bug, Task, etc.).
- User Story ID (optional) – If you want to report the issue under a specific User Story, enter the User Story ID in this field. The issue will then be created as a child item under that User Story in Azure DevOps (This option is available only if the Azure project is configured to allow this relationship).
- Issue Name – Enter the title of the issue.
- Description – Includes the information entered in the Actual Result field of the failed step during the test run.
Once the details are filled in, proceed with creating the issue. The bug will be created in Azure DevOps according to the selected configuration.
The new Azure Work Item will be connected to a new PractiTest issue. The Name, Description, and Issue’s state in Azure will be synced to the equivalent PractiTest’s issue.
If the description field is not visible in your Azure work items by default, you can add it to the relevant work item type (the integration works with the ‘Bug’ item type) by following these steps:
- Click on the three dots on the top right corner of your screen, then select ‘Customize’.
- Click the ‘New Field’ button at the top of the screen.
- Check the ‘Use an existing field’ checkbox, then select ‘Description’ from the drop-down list. Click on ‘Add field’.
Note: if you don’t see all Azure DevOps projects you integrated with PractiTest when creating a new issue, please go to the Account Settings – Integrations tab – press on the ‘Update and Get Projects’ button.
Linking an Existing Issue
The link existing issue option allows you to link issues that already reside in your PractiTest project. If you want to link a work item directly from Azure, you can import it from within the test run, and link it to the test step.
Importing Requirements
Click on the down arrow next to the ‘New Requirement’ button and select the ‘Import a Requirement’ option. This will help you choose any work item you want to import into PractiTest. You can import work items in bulk, by separating their IDs by commas. After the work item was imported, you can link it to your test cases via the Traceability tab in order to create traceability links between them.
Note: When importing requirements, state the work item system ID in Azure without the Prefix you selected when configuring the integration (numeral values only).
Synchronizing Issues
If you want to import existing work items from Azure DevOps as Issues in PractiTest, you can click on the down arrow next to the ‘New Issue’ button, and select ‘Sync a new Issue from Azure DevOps’. Paste the numeral value of your Azure DevOps work item/s. You can Sync issues in bulk, separated by commas.
Field Mapping
Note: Field sync needs to be configured for each PractiTest project separately.
In the project settings, navigate to the Integration tab and choose ‘Azure DevOps project mapped fields’.
1. Choose the Azure field you want to map. You can map the following fields to PractiTest:
| Field Type in Azure DevOps | System/Custom Field | Mapped Field Type in PractiTest |
| Text (Single line) | Custom | Text |
| Text (multiple line) | Custom | Memo |
| Picklist (String) | Custom | List |
| Picklist (Integer) | Custom | List |
| Date/Time | Custom | Date |
| Integer | Custom | Number |
| Priority | System | Priority |
| Severity | System | List |
2. Tick the “Add to ‘Fail & Issue’” box if you want this field to appear when reporting an issue from PractiTest to Azure DevOps.
3. Choose if and where you want to map this Azure DevOps field, for example, to a PractiTest dedicated field, or to the description of the PractiTest entity.
Note: If you choose to map it to a field, the list of PractiTest fields that will appear will contain only custom fields that match the type of the Azure DevOps field you chose (for example, number-number).
Once you choose to map to fields, you will need to choose whether to present the data in the issues field, the requirement field, or both. If the PractiTest field you choose is linked to only one of them, then you will have only that option to map to.