In this release, we have added two quite interesting approaches for testing SAP PI/PO.
Dual stack
If you have an SAP PI dual-stack system with classical scenarios and want to test your migration, you can now fetch messages from the dual stack and create test cases. This is perfect for migration projects, where you want to test if everything works as expected. We have developed on our 7.4 dual-stack system, and successfully fetched data from clients 7.1 system. There will be some issues with older systems, but you can create test cases. You can read more about the dual stack option here.
Secure messages
This is the big challenge with Record Replay scenarios. Where you take production data and rerun it on your development system.
We created Figaf based on the assumption that real production data is what needs to be used for testing because it contains the difference in the data. Unfortunately, most of it is sensitive and it could have implications for SOX and GDPR.
That means everybody with access to Figaf can get access to the messages, so it creates a loophole in the SAP security. This means that, for example, external consultants may be able to get access to sensitive data.
We already have an approach for handling the anonymization of data. It does require the developer to understand what is sensitive and it can be multiple values, and it will not work to test migration. Potential clients with a lot of confidential data wanted to perform a migration, but it would be difficult to anonymize all interfaces. They wanted a solution to ensure end to end anonymization without external developers would have access to the payload.
If you create test data on your productive system, the Figaf DevOps Suite will ensure that all developers only see scrambled data. This way they are able to see if there is something wrong with a specific field. They can see what field is affected and may be able to derive some information. They will not be able to see the specific data. If there is something they don’t understand, they can ask an admin to view the difference.
I think this security will make it a lot easier to outsource regression testing because you don’t risk them getting access to secret data.
Improved synchronization process
For customers with a lot of SAP standard components, our synchronization did not work. The simple query API we used timed out when listing datatypes etc. We are now only synchronizing the SAP objects that are referenced from any other objects. That way you only synchronize the real used objects.
You can read more and see the demo here.
Improved comparison of SAP CPI iflows
We have improved the algorithm to show what objects were used in an SAP CPI iflow. You can now see which artifacts have been modified between two versions.
Java 11/OpenJDK
If you don’t want to use the Oracle Java license, we now also support Open JDK 11. You, therefore, don’t have to use a Java License.
Try it now
You can start a free trial of the Figaf DevOps Suite.
