226 Microsoft Team Foundation Server Synchronization)minisites.qaiglobalservices.com/stc2012/Paper_...
Transcript of 226 Microsoft Team Foundation Server Synchronization)minisites.qaiglobalservices.com/stc2012/Paper_...
HP Quality Center – Microsoft Team Foundation Server
Synchronization
© 2009 Wipro Ltd - Confidential
Synchronization
RUPESH GARG & SRIRAHUL MANNEM
Agenda
Need for Integration
Overview about QC and TFS
Challenges faced during Synchronization
Proposed Solutions
© 2010 Wipro Ltd - Confidential2 © 2010 Wipro Ltd - Confidential2
Framework design and Process
Outcome of Synchronization
Benefits
Q&A
Need for Integration
INTRODUCTION:
In the real time project environment, we have fair number of customers where the
development team uses TFS but the QA team uses HP Quality Center. There has
been a growing interest in interoperability between TFS and Quality Center that
allows developers and testers to work more closely together.
There are other tools which can be integrated with Each other like Jira and HP Quality
Center.
© 2010 Wipro Ltd - Confidential3 © 2010 Wipro Ltd - Confidential3
Center.
Project artifacts like requirements, test cases and defects in each management tool
can be integrated with other.
We will focus on QC, TFS integration for defects module
Quality Center:
• HP Quality Center software is a scalable, unified platform for managing and automating the
delivery of secure, reliable, quality applications. HP Quality Center software enables you to
implement a complete quality management infrastructure, establish consistent, repeatable
processes and best practices for managing requirements, tests and business components.
Key Benefits:
Overview about QC
© 2010 Wipro Ltd - Confidential4 © 2010 Wipro Ltd - Confidential4
Key Benefits:
• Prioritize testing based on business risk
• Access testing assets anytime, anywhere
• Schedule and execute tests automatically, 24X7
• Analyze readiness with integrated graphs and reports
• Manage defects and trace them to tests and requirements
Team Foundation Server:
Visual Studio Team Foundation Server 2010 (TFS) is the collaboration platform at the core of
Microsoft's application lifecycle management solution. TFS automates the software delivery
process and gives you the tools you need to effectively manage software development projects
throughout the IT lifecycle.
Key Benefits:
Overview about TFS
© 2010 Wipro Ltd - Confidential5 © 2010 Wipro Ltd - Confidential5
Key Benefits:
• Increases productivity, as the team shares best practices for development and deployment,
and developers need focus only on current business requirements.
• Improves quality, so the final application meets the needs and expectations of users.
• Breaks boundaries through collaboration and smooth information flow.
• Accelerates development through simplified integration.
• Cuts maintenance time by synchronizing application and design.
• Increases flexibility by reducing the time it takes to build and adapt applications that support
new business initiatives.
• Difficulty in defect management due to different tools used by development
and test teams:
Development team uses Microsoft Team Foundation Server (TFS), QA team uses HP
Quality Center (QC) for defect management. So developers cannot view the defects
raised by the QA team and QA team cannot view the updates of defects from TFS
• Different defect life cycles:
CHALLENGES FACED DURING SYNCHORNIZATION:
© 2010 Wipro Ltd - Confidential6 © 2010 Wipro Ltd - Confidential6
• Different defect life cycles:
Both TFS and QC has their own defect life cycle. Establishing a synchronization between
QC and TFS has become a major challenge.
So process has to be built for establishing a common defect life cycle process which suits
for both the life cycles
Proposed Solution
• Standardization of defect life cycle: As a first step, we standardized a work flow which can satisfyboth TFS and QC defect life cycles; hence development team and testing team have a same
interpretation and maintain a transparency. A Common Defect Life cycle is established that suits for both
QC and TFS.
For example below table gives a snapshot how defects can be interpreted by development and test
team.
© 2010 Wipro Ltd - Confidential7 © 2010 Wipro Ltd - Confidential7
Proposed Solution
• ALM Synchronizer for defect management: The appropriate solution would be to
synchronize TFS and QC so that developers and tester would be viewing the
defects raised/updated by each other. To accomplish this, HP ALM Synchronizer
has been carried out to perform Uni/bi-directional synchronization between QC
and TFS
© 2010 Wipro Ltd - Confidential8 © 2010 Wipro Ltd - Confidential8
Frame work Design
HP ALM Sync Client
HP ALM Sync Server
End Point 1
HP QC
End Point 2 TFS
HP ALM Synchronizer Client: Displays current links, and provides a user interface for the user to create and manage links, and run link tasks. Sends requests from the user to the
Synchronizer server.
© 2010 Wipro Ltd - Confidential9 © 2010 Wipro Ltd - Confidential9
Synchronizer server.
HP ALM Synchronizer Server: Synchronizes data between HP Application Lifecycle Management (ALM) and other applications. Manages synchronization and communication
between endpoints. In addition, the server manages connections to link endpoints using the
endpoints’ application programming interface (API), which must be installed on the server
machine.
End Points: End Point 1 is HP Quality Center, End Point 2 is Microsoft Team Foundation Server
Frame work Design
Step by Step Process:
Step 1: Creating Links: Synchronizer provides a wizard that enables the user to create a link.
For each link, User can assign a name and description, and define its two endpoints. One
endpoint is always an ALM instance that is Quality Center; the other endpoint is the project in
the application user wants to synchronize that is TFS.
© 2010 Wipro Ltd - Confidential10 © 2010 Wipro Ltd - Confidential10
Frame work Design
Step by Step Process:
Step 1: Creating Links: On Clicking on Next button ALM Synchronizer will check the
connectivity for 2 end points on providing the valid connection details
© 2010 Wipro Ltd - Confidential11 © 2010 Wipro Ltd - Confidential11
Frame work Design
Step by Step Process:
Step 1: Creating Links: This step shows the choosing the entity to be synchronized between
QC and TFS.
Since bug synchronization is the goal, select ‘Defect’ in the first Endpoint and ‘Bug’ in the
second Endpoint. On Clicking the button ‘Finish’ the Link Creation process will be completed.
© 2010 Wipro Ltd - Confidential12 © 2010 Wipro Ltd - Confidential12
Frame work Design
Step by Step Process:
Step 2: Setting Filter Options
After the link creation is established, User has to define filters to be used during
synchronization. When Synchronizer looks for new records that have been created in the
endpoints since the last synchronization, it includes only records that match the selected filters.
© 2010 Wipro Ltd - Confidential13 © 2010 Wipro Ltd - Confidential13
Frame work Design
Step by Step Process:
Step3: Setting Scheduling Options
Synchronization can be scheduled at particular time by Enabling the Schedule option
Schedule every: Runs incremental synchronization tasks for the link at the specified time
interval.
Run task at: Runs incremental synchronization tasks on the link at the specified time each day.
By default, tasks run every day.
© 2010 Wipro Ltd - Confidential14 © 2010 Wipro Ltd - Confidential14
.
Frame work Design
Step by Step Process:
Step 4: Configuring Rules for Defects Synchronization
After the user has defined the basic properties for the link, and set scheduling and filters
options, User has to define the type of synchronization (Incremental or Full Synchronization) to
be performed on each endpoint.
.
© 2010 Wipro Ltd - Confidential15 © 2010 Wipro Ltd - Confidential15
Frame work Design
Step by Step Process:
Step 5: Creating Field Mappings
The Mapping of Fields between two endpoints is made easy in this enhanced GUI
• Select a field from the EndPoint1 (HP-ALM Defect Schema) and then select a corresponding
field to be mapped in the EndPoint2 (TFS Bug Schema).
• Click the option ‘Map selected Fields’ then select the direction to be synchronized. Mapped
entities are displayed in italics as shown in the screenshot.
© 2010 Wipro Ltd - Confidential16 © 2010 Wipro Ltd - Confidential16
.
Frame work Design
Step by Step Process:
Step 5: Creating Field Mappings
• Make sure that all mandatory fields of both Endpoints are mapped. (Note: The mandatory
fields are those marked with Red Flags).
• If any fields to be mapped are read-only (like TFS_ID, Created Date, etc), then make that as a
unidirectional mapping.
• The direction can be later edited using the ‘Mapping Properties’ window next to Mapped
Fields Window.
© 2010 Wipro Ltd - Confidential17 © 2010 Wipro Ltd - Confidential17
Frame work Design
Step by Step Process:
Step 6: Run Integrity Check
Execute the integrity check to make sure the links are established correct between TFS and
QC. On successful completion of integrity check, we can enable the Integration link created
which will initiate the synchronization process at both the ends (QC, TFS)
After completing the First 5 steps click the Save button (on top of all tabs), which shows the
displays the following pop-up asking to do Integrity Check for the Link. Click ‘Yes’.
© 2010 Wipro Ltd - Confidential18 © 2010 Wipro Ltd - Confidential18
displays the following pop-up asking to do Integrity Check for the Link. Click ‘Yes’.
.
Frame work Design
Step by Step Process:
Step 6: Run Integrity Check and Two way/One way Synchronization
On Successful completion of Integrity check the Synchronization is now complete and Synch
process can be executed either manually or using Scheduler
© 2010 Wipro Ltd - Confidential19 © 2010 Wipro Ltd - Confidential19
.
Frame work Design
Demo – Two Way Synchronization
We can see how the defects in QC and TFS are synchronized with each other using a Two-Way
Synchronization
.
Scenario: Already 5 dummy defects are already created in QC, a Fully Synchronization is
executed to copy all the defects to TFS.
© 2010 Wipro Ltd - Confidential20 © 2010 Wipro Ltd - Confidential20
The recording shows how the Defects in QC and TFS are updated after synchronization.
WRF File
Outcome of Synchronization
Outcome:
• Every new/Selected defect in Quality Center, after synchronization will create a matching work item
in TFS (with a http link to original defect)
• Every new/Selected work item in TFS, after synchronization will create a matching defect in Quality
Center
•When a new work item is created in TFS using synchronization, attachments and hyperlinks from
Quality Center defect are copied over to TFS
•When new defect is created in QC using synchronization, attachments and hyperlinks from TFS are
© 2010 Wipro Ltd - Confidential21 © 2010 Wipro Ltd - Confidential21
•When new defect is created in QC using synchronization, attachments and hyperlinks from TFS are copied over to QC
• New attachments and hyperlinks for existing QC defect will be copied to corresponding TFS work
item after the synch process is executed
• New attachments and hyperlinks for existing work items in TFS will be copied to corresponding QC
defect after synch process is executed
Benefits of Integration
Benefits:
• Up date status of the of Defect Details at one place ( TFS/QC)
• Transparent defect status which help in planning the test cycles. Good Control over the Testing
Defects Status
• Avoids Communication gaps between Development and Testing teams
• Improves Quality on Defect Tracking process, with effective defect tracking
• Uniform interpretation across the projects
© 2010 Wipro Ltd - Confidential22 © 2010 Wipro Ltd - Confidential22
• Uniform interpretation across the projects
• Number of duplicates reduced due to transparent operations
• Risk mitigation and contingency plans can be derived easily.
• Customized template which can be reused in future projects hence it’s a value add to the
customers.
• Unique defect life cycle management for customer.
Thank You
Your Name
Designation
© 2009 Wipro Ltd - Confidential
Designation