Microsoft Team Foundation Server (TFS) is used by several enterprises to manage their development work whereas HP ALM/QC (Now known as Micro Focus ALM) is extensively used for its quality control module. Integrating these two systems can, therefore, help remove the visibility ‘black hole’ between the development and the quality control teams; thereby, eliminating the possibilities of miscommunication, delayed communication, or exchange of incorrect/outdated data. HP QC integration with TFS further ensures that both teams have complete visibility into each other’s tasks in real time and they are on the same page regarding delivery timelines & quality parameters.
Let us look at a potential real-life scenario to understand how HP ALM TFS integration can help teams an enterprise work efficiently.
A Product Manager, based on his/her communication with the customer, creates a ‘User Story’ with descriptions and delivery timeline in TFS. The development team also using TFS breaks down the ‘User Story’ into multiple ‘Tasks’ and develops an elaborate plan with timelines, effort hours, and assignees for each task. The ‘User Story’ also synchronizes to HP QC, which is being used by the quality control team. The quality control team, therefore, simultaneously starts writing a test case for the given ‘User Story’.
At this given scenario, if there is a change in the ‘User Story’ due to reasons such as customer adding new features or a change in the delivery timeline due to change of business priorities at the customer end, an update made to the ‘User Story’ will simultaneously be seen by development team users as well as by quality control team users. Synchronization of this information in both systems in real-time will help the teams not only hold & re-prioritize their tasks, but also get a context of the business scenario at the customer’s end.
Benefits of integrating HPQC and TFS:
- 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
Now, imagine, both teams take care of the new request and new delivery timelines in their updated plans and the development team completes work on the ‘tasks’ according to the updated timelines. After completion of all the ‘tasks’, the development team closes the ‘User Story’ at their end. The status change for the ‘User Story’ also reflects in HP QC and then the quality control team knows that they can run the test case as per their schedule.
If the integration is configured bi-directionally between HP QC and TFS, the status of the test result from HP QC can also be synchronized to the ‘User Story’ in TFS giving the Product Manager as well as the development a real-time visibility into completion of their tasks.
OpsHub Integration Manager supports the integration of multiple HP ALM versions (from 10.0 to 12.55) and all versions of TFS (including the Cloud version, VSTS). The popularly synchronized entities between these two systems are:
The seamless bi-directional integration between these systems helps teams in saving time as they do not have to manually feed in data in multiple systems or worry about data discrepancies. As access to the business requirements, development status, and associated updates as well as quality parameters, Quality Assurance (QA) schedule, test cases, and test results are available to all the relevant stakeholders in the enterprise at any given time, it also becomes easier for them to take independent as well as collective decisions.
To read more blogs from our team of integration & migration experts, click here