Signavio, SAP Cloud ALM and Tricentis Test Automation
Video from 11/4/2024
Please enable videos in our privacy settings
Test automation should follow the same governance structures as the software changes to be tested themselves. This example shows how Conigma™ Connect not only synchronizes changes between SAP Signavio and Tricentis Tosca Cloud - also called Tricentis STA -, but also delivers the corresponding governance structures in SAP Cloud ALM. This would work the same way with Conigma™ CCM, Jira, ServiceNow, Azure DevOps and any other ALM software.
In this example, a business process first is created in SAP Signavio. From this, Conigma™ Connect automatically generates the corresponding governance structure in SAP Cloud ALM. This consists of a project task and a sub-task, here called a creation task. In parallel, Conigma™ Connect breaks down the BPMN model into individual steps, maintains the library of Resuable Test Steps in Tricenctis STA and creates a skeleton for a test case.
But what happens if the business process in SAP Signavio is updated? For example, deleting a task from the business process in SAP Signavio or inserting a new task? Conigma™ Connect also plays a central role here. First, Conigma™ Connect adds another sub-task to the original project task, called an update task here. In addition, Conigma™ Connect adapts the reusables library. The new task added to the business process in SAP Signavio is automatically created in the Tricentis library. The deleted task is marked as obsolete in the Tricentis library. The update task in SAP Cloud ALM visualizes all differences between the last and the current business process revision from SAP Signavio as a transparent basis to finalize the test cases changed by Conigma™ Connect in Tricentis.