Helix ALM – Azure DevOps Server (TFS) Integration Overview
In an Application Lifecycle Management (ALM) environment, the choice of systems, and the collaboration between the cross-functional teams play a great role in delivering quality solutions. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements. Best-of-breed systems such as Helix ALM and Azure DevOps Server (TFS) bring rich functionalities to the ecosystem.
By integrating Helix ALM and Azure DevOps Server (TFS), the development teams will have real-time visibility into the test cases, QA schedule, and test results, and the quality control team will have access to complete context of the user story as well as any change/enhancement to it. When these two teams collaborate seamlessly, the overall collaboration in the ecosystem increases and enterprises deliver better quality products to customers at a faster pace.
How Helix ALM – Azure DevOps Server (TFS) integration is beneficial for an enterprise
- Access to QA plans and defects in real time
- Real-time updates on the status of a story, its estimated time of delivery, and any risks that might delay the impending release
- Complete context of the customer requirement and visibility into codes written by the development team & test cases written by QA team
- Coordinate on the delivery timelines seamlessly with concurrent updates on changes
With Helix ALM + Azure DevOps Server (TFS) integration, enterprises can:
How OpsHub Integration Manager integrates Helix ALM and Azure DevOps Server (TFS)
OpsHub Integration Manager integrates Helix ALM and Azure DevOps Server (TFS) bidirectionally. It ensures that all historical and current data is available
to each user, in that user’s preferred system, with full context, in real-time. All ‘user stories’ Azure DevOps Server (TFS) automatically synchronize to Helix ALM and all the defects associated with the ‘story’ synchronize back to Azure DevOps Server (TFS).
Popularly synchronized entities
Use Case: Helix ALM integration with Azure DevOps Server (TFS)
Problem statement: The development and quality control team start work on adding a new feature to an existing application. The customer changes some requirements once the work has already begun. The Product Manager updates the ‘requirement’ in the development system. The development team incorporates the changes in the user story, but the quality control remains unaware about the change until development team sends the user story for testing.
Solution: When the Azure DevOps Server (TFS) and Helix TCM (test module in Helix ALM) are integrated, there will be no need of manual communication between the two teams. Any changes made to one system will reflect in both the systems.
- The Product Manager creates a ‘requirement’ in Azure DevOps Server (TFS) and attaches a screenshot that includes communication details from the customer.
- The ‘requirement’ synchronizes to Helix TCM. The quality control team writes test cases according to the requirement.
- The Product Manager updates the ‘requirement’ after receiving additional input from the customer. The updates synchronize to the ‘requirement’ in Helix TCM.
- The quality control team starts work on revising the test cases as per the new ‘requirement’.
Benefits of integration for Helix ALM and Azure DevOps Server (TFS) users
Helix ALM users
- Real-time updates on the story and associated changes/enhancements
- Access to the development status from within Helix ALM
- No manual efforts needed to keep backend teams updated on the QA cycle and reports
Azure DevOps Server (TFS) users
- No duplication of efforts for entering the same data in multiple systems
- Clear visibility into quality parameters and test results in real time
- No manual efforts needed to keep quality control teams updated on the development cycle