KJ Ross performed research and development for Microsoft to help bridge the gap between development and testing software. Download this case study as a one page PDF here.
With many clients using Microsoft’s Team Foundation Server (TFS) as their collaboration platform for automated software delivery and HP Quality Center (QC) as their Test Management tool, the need to bridge the gap between development and testing was identified as a key challenge many clients are facing and will face.
The central repository for test cases and defects is HP Quality Center. Developers using TFS need to have access to test cases and defects when reviewing and fixing defects.
HP has a “sanctioned” synchronisation tool available to customers who already have access to a HP ALM or Quality Center license. This tool allows synchronisation between HP Quality Center Defects and/or Requirements and the following related areas within Microsoft TFS. The solution was delivered with HP ALM – Quality Center 11.00 and TFS VS2010. The following versions are also supported: QC 9.2, QC 10.0; TFS2008.
Configuring this tool to synchronise between QC and TFS, KJ Ross was able to successfully bridge the information flow of defects between the two tools. The configuration of the synchroniser is done based on the current test processes that are implemented within the business; an assessment is used to establish this.
After development effort we were able to customize the QC Defect and the TFS Bug Work Item so that synchronization could occur. Customisation of QC workflow was also carried out so that Test Case information is passed over to the TFS Work Item, which provides the information to the developers without them having to access QC and use QC licenses.
- KJ Ross is able to customize QC workflow in a way to provide developers with as much information as they require; all steps, expected and actual results are attached to the QC Defect and then synchronized to the TFS Bug
- KJ Ross is able to customize TFS Work Items so they are structured in a way to follow the standard defect template being implemented throughout the client’s project.
- Defects are kept synchronized between the two tools at least every 5 minutes