Link Tricentis qTest and SAP Solution Manager ChaRM

by Malte Klassen

This video shows a SAP Solution Manager ChaRM - Tricentis qTest integration.
First, an RfC is created in ChaRM. This creates a qTest Requirement. These two entities are linked bidirectionally, so that all data always remains consistent, no matter on which side you change.
After scope extension in ChaRM and running through the qTest test procedures, qTest Defects are created.
These defects create ChaRM incidents that are associated with the original RfC. Again, if changes are made on either side, bidirectional integration keeps the data consistent.

First, an RFC is created first in ChaRM.
After running the scope extension and approval procedure, a qTest requirement is created automatically via Conigma Connect.
A click on the URL generated by Conigma Connect leads to the qTest entity.
ChaRM RFC and qTest requirement are now seamlessly linked. For example, a status change on the left side is synchronized real time to the right side.
The requirement status in qTest has been pushed to “In Progress” by automatic synchronization.
Of course, the synchronization goes in both directions. Here, for example, the requirement’s description in qTest is changed. This leads to the corresponding automatic update in SAP Solution Manager ChaRM.
Conigma Connect again ensures seamless integration. Here you see e.g. the ChaRM RFC with the corresponding URL.
After test definition and execution, the qTest defects can be created.
Saving a qTest defect leads to an automatic creation of an incident in SAP Solution Manager ChaRM.
The link to the ChaRM incident has already been automatically maintained on the qTest defect.
The ChaRM incident correctly belongs to the initially created RFC in SAP Solution Manager.

The integration shown here addresses only one possible data model. With nearly no effort, e.g. Focused Build for SAP Solution Manager Work Packages can be linked to qTest Requirements, as well as Defects on both sides. The same applies for SAP Cloud ALM, ServiceNow entities as well as for the ones from Jira, Azure DevOps or products like Broadcom Rally.
Everything out-of-the-box via no-code customizing.

Go back