Bidirectionally connect Tricentis qTest with ServiceNow
by Malte Klassen
This video shows an example of a ServiceNow - Tricentis qTest integration.
First, a change request is created in ServiceNow. A push to the status "Scheduled" ensures the creation of the partner requirement in qTest. These two entities are linked bidirectionally, so that all data always remains consistent, no matter on which side you change. After running through the qTest test procedures, qTest defects are created. These defects create ServiceNow incidents that are associated with the original ServiceNow change request. Again, if changes are made on either side, bidirectional integration keeps the data consistent.
In the current example, a change request is first created in ServiceNow. Approval of the change request moves it to the "Scheduled" status. A status change to "Implement" ensures automatic creation of the qTest requirement. Among other things, this automatically maintains the URL linking the requirement. A bidirectional integration ensures data consistency at any time. Here an example of an update in the requirements description. This update real time is transferred to the short description of the ServiceNow change request. An execution of the test procedures ensures that qTest defects can be created in case of corresponding test results. Here you can see the automatically created ServiceNow incident, which is linked to the original ServiceNow change request. For example, the correction of the typo real time is synchronized. Here you can see the synchronized correction and the URL of the qTest defect.
The integration shown here addresses only one possible data model. With nearly no efferot, e.g. ServiceNow Request Items can be linked to qTest Requirements. The same applies to qTest integrations with Jira, Azure DevOps, Broadcom Rally, SAP Solution Manager ChaRM, Focused Build for SAP Solution Manager or SAP Cloud ALM.
Everything out-of-the-box via no-code customizing.