Testing is not really fun. But you need to perform it.
Making a good unit test for SAP CPI and testing full iflows is one of the more complicated processes. You could create some test cases but it became pretty difficult to manage.
1) Testing with mock services. This is useful if you have systems like SuccessFactors that you cannot call when you want to run regression tests. Then the Figaf tool will replace calls to SuccessFactors and replace them with an HTTP call to Figaf. In the request, it will inject the expected response. So you get to test scripts, routing, and flows.
2) Secured testing. The best test data you have is from production. This is in many cases confidential like HR data. You, therefore, do not want all your developers to see the information. That is why we have added secured testing. This ensures the payloads are masked in the Figaf tool, so normal developers only see masked data. So they will be able to determine something is wrong but not get the name of the person.
We have written a lot more about the secured testing that also is for SAP PI/PO.
You can see how this works in the following video.
Watch on YouTube SAP CPI secure testing and mocking
3) Groovy unit tests based on the Figaf test cases you have. This is a simple way to test all your groovy scripts in an Iflow. We have bundled this with the Git integration to make it possible to run the development process simpler. This allows you to run and debug your groovy scripts and it is a lot faster to develop in that way.
Watch on YouTube SAP CPI development with Git and IntelliJ using the Figaf tool.
Try it out
You can start a free trial of Figaf DevOps Suite. You can get started in less than 60 minutes to see what the tool is able to do.
If you have any questions, email info@figaf.com and we will answer your concerns.
