Micro Focus ALM Synchronizer Defect Management Tool Hands-On Tutorial

Introduction and background of Micro Focus ALM Synchronizer, previously known as HP ALM Synchronizer:

Micro Focus ALM Synchronizer might be a new phrase for many and can evoke numerous queries when encountered for the first time. When facing an unfamiliar term, we typically resort to a Google search to gather more information. However, the available information for Micro Focus ALM Synchronizer is rather sparse and includes only a few installation guides, images, and descriptions.

In order to fully comprehend the workings of this tool, it’s helpful to have a tutorial or article written in layman’s terms, particularly for those new to Micro Focus ALM Synchronizer. This is why I am presenting this topic to you all. I count myself lucky to have had the chance to work with this tool and gain a thorough understanding of it.

This article delivers an in-depth understanding of the role, significance, and functionality of the Micro Focus ALM tool. It also provides a download link and step-by-step instructions for your convenience. If you are new to this tool, this article will serve as a beginner’s guide.

Overview

Micro Focus ALM Synchronizer is a beneficial and handy tool for organizations where developers utilize Defect Management tools like TFS (Team Foundation Server), and testers/QA use other tools such as QC/ALM (Quality Centre/Application Lifecycle Management).

Let’s delve into more detail about its operations!

Micro Focus ALM Synchronizer is a Defect Management Tool that ensures a smooth transition of defect management between developers and testers. Managing defects is an essential component of testing, thus having a tool that guarantees flawless defect management across the organization is key.

Next, let’s address the question – what functions does Micro Focus ALM Synchronizer perform and how does it operate?

To provide an answer, let’s proceed with the tutorial set out below.

Role of This Tool

This tool assists in the synchronization of data between Micro Focus ALM and other end-points. For the purpose of this tutorial, we will view Micro Focus ALM and TFS as two end-points.

Below is a diagram demonstrating the synchronization process between the two end-points:

‘Micro Focus ALM/QC’ is a tool deployed by testers/QA for managing defect-related data. ‘TFS’ is utilized by developers for the same purpose.

When testers modify defects in QC, it is crucial that developers remain informed about these changes. This tool bridges the communication gap between developers and QC/ALM in organizations that predominantly use TFS or similar tools for defect management.

Download Info

The Micro Focus ALM Synchronizer Client and Server can be downloaded from the Micro Focus website. Before downloading, ensure that you verify the versions of the two end-points.

Example: If the versions of Micro Focus ALM and TFS are 12.2, download the 12.2 Synchronizer Client on the local machine where the synchronizer will be run.

Before you can download the client, you must sign up for a Micro Focus Passport and log in to access the software and installation guide documentation.

Here is the registration link: Download Link

You can create an account on the official Micro Focus website, and then log in to download the software based on your requirements.

If you require any help with the installation guide and documentation, you can check the tool’s help menu.

Need of This Tool

After providing an overview of this software, let’s elaborate on why the Micro Focus ALM Synchronizer was needed and what it does.

Let’s review the responses:

#1) Integration: This tool enables integration between TFS and QC/ALM, leading to improved coordination between testing and development teams.

#2) Synchronization of QC Defects with TFS Bugs: When a tester records a defect in QC, all pertinent information is mapped directly into TFS. This keeps developers up to date with new defects and their details.

#3) Error Handling Support: Synchronizers come with an error handling feature to quickly identify and fix errors. The Advanced tab allows you to notify specific group email addresses about errors.

From my previous experience, I was tasked with recognizing and fixing errors in my company. This job required training and expertise to handle different error types.

#4) Defect Management: With this tool, defect management becomes easier by mirroring/syncing fields in QC Defect IDs with corresponding TFS IDs (e.g., severity, defect description, etc.).

Below is a screenshot of the tool interface:

In the screenshot above, you can see several tabs and links on the left-hand side. We will look into these links in the upcoming section.

Links to ALM Synchronizer

In the case of Synchronizer, links contain details about the end-points and define which entities are included in the synchronization and how the synchronization is carried out.

Key points to consider:

• Typically there are two links, named as per organizational convenience.
• For clarity, we can name them Link1 and Link2.
• In ALM/QC (endpoint1), defects are termed as ‘Bugs’, and in TFS (endpoint2), they are referred to as ‘Tasks’.
• All related data, such as general information, connection specifics, field mapping, and scheduling, must be updated for both links.
• Links should be enabled to operate the synchronizer.
• By right-clicking on a link, you can run the synchronizer by choosing the appropriate option (Incremental, Full, or Integrity Check).

These points cover the basic operations with links in this tool.

Tabs of This Tool

Let’s provide a brief description of each tab to better understand their roles:

#1) General Tab: This tab shows general details about both end-points, such as end-point names, types, details of synchronization runs, and reports of success, failure, and errors.

#2) Connectivity Tab: This tab contains connection specifics like usernames, passwords, and allows you to test the connectivity between the end-points.

#3) Scheduling Tab: This tab offers details about the scheduled synchronizer runs for each link, including timing settings for both endpoints.

#4) Filters Tab: This tab gives you the ability to set up filters for data synchronization by specifying queries for each link.

#5) Events Tab: This tab establishes rules for record creation, updates, and deletions in both end-points.

#6) Field Mapping Tab: This tab is vital as it defines the mapping of fields between the end-points. It allows bidirectional or unidirectional mapping depending on the specific requirements.

#7) Advanced Tab: This tab presents advanced features for error management and notification.

Next, let’s understand how the Synchronizer truly works!

Working of Micro Focus ALM Synchronizer

Here’s how the Synchronizer functions:

• During the synchronization process, users establish input and output criteria. Inputs can come from either end-point, and synchronization is executed based on these settings and mappings.
• For each selected defect in QC, a corresponding work item is generated in TFS, and vice versa. This ensures that all changes in defects are synchronized between the end-points.
• Updated defects in QC are also mirrored in the respective work items in TFS.
• Selective values such as severity and priority are synchronized among defects.
• Attachments are also synchronized between TFS and QC.

Next, let’s look into the potential errors that you could encounter when operating Micro Focus ALM Synchronizer and how to rectify them.

Errors while Working with this tool

When several people work in a team environment, the likelihood of errors increases. Nonetheless, it’s crucial to identify and fix errors as quickly as possible. Here are a few common types of errors:

#1) Incorrect Value Entered:

In the process of managing a QC defect, someone might enter the description incorrectly or with unnecessary spaces or symbols. To rectify this, review the defect history in QC to determine who last modified it and inform the relevant individual to correct it. It’s suggested to let the concerned individual manage the correction. Once the correction is done, operate the synchronizer and review the report for any issues.

#2) Document Issue:

Attachments to defects could have an inappropriate size or format, leading to FAILED/UPDATE/DELETE ATTACHMENTS errors. To rectify this, make sure you inform the relevant individual to upload the documents in the required size and format.

#3) Blank Value in Mandatory Fields:

If mandatory fields are left empty, this will trigger an error. To fix this, ensure that the relevant person updates the fields accurately and operate the synchronizer to check the results.

Now, let’s proceed to the different types of Micro Focus ALM Synchronizer!

Types of Micro Focus ALM Synchronizer

Micro Focus ALM Synchronizer provides several types of synchronizers to cater to specific requirements. These synchronizers can be scheduled to operate at designated times to ensure accurate synchronization of updated and newly created records. The types of synchronizers include:

#1) Incremental Synchronizer

The Incremental Synchronizer operates when alterations or increments are made. It recognizes records created or modified since the last synchronization task and executes synchronization based on the preset settings and mappings.

#2) Full Synchronizer

The Full Synchronizer carries out a complete comparison of records in each end-point. It offers details about records that were not synchronized in an Incremental run. As a result, all records are synchronized when the Full Synchronizer is run.

#3) Integrity Check

The Integrity Check differs from the other types of synchronizers. It is executed when creating a new link or modifying an existing one. The Integrity Check should be undertaken with precision, as a failure in this check deactivates the link and prevents synchronization.

Conclusion

In conclusion, Micro Focus ALM Synchronizer is a tool that streamlines defect management between developers and testers. By setting up the end-points and their associative fields, scheduling routine synchronizer runs, and inspecting the detailed reports, effective defect management can be achieved. This tool encourages transparency and cooperation between developers and testers.

Those who have had the chance to work with this tool understand its significance. I feel both excited and grateful to have acquired knowledge and hands-on experience with this advanced tool.

About the author: This post is authored by Varsha G., a member of the STH team.

If you have used this tool, please share your experience in the comments section below.