Posts

SAP CPI Testing, now with Mock and secured data

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 if you have SuccessFactors systems you cannot call once 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 can 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 ensured 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 to 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.

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 allow you to run and debug your groovy scripts and it is a lot faster to develop in that way.

Try it out

There is free trials of the tools at https://figaf.com/irt. You can get started in less than 60 minutes to try out what the tool is able to.

If you any questions email info@figaf.com and we will answer your concerns.

Secure your SAP PI/PO and CPI test cases

Testing is important for your interfaces. For migration and bug fixes it is important to be able to perform regression tests.

The place you can create the best test data from is from your productive systems, where customers are creating orders with 100 lines with 10 different product types. It is not only from the clinical approach from a user test. You need both.

The bad thing about the production data is, it often contains confidential data. Social security number, payroll data or customer information. It can, therefore, lead to problems if you want to test with it. You may often have externals working on your systems and don’t give them access to confidential data.

Scrambled comparison, user can see there is something wrong but not content

We had to solve this problem with the new innovation. You simply select any of your SAP PI/CPI systems you have connected to and specify that they are confidential. Then all test cases created from that system will be marked as confidential. Then it will only be possible for users with the role IRTSensitivePayloadViewer, to view the original data. Otherwise, you can only see the scrambled version as seen in the image.

It is only possible to run the test on the system marked as secured. With secured systems is meant that it is systems is configured so users cannot view the payloads being processed. We are working on ways to block confidential messages only. It will be a component to filter out the messages and using the web dispatcher.

You can see a video about the testing functionality here.

Over the next patches, we will enable some more functionality like

  • Blocking viewing messages of SAP PI, so you can view your normal test messages
  • Testing SAP CPI with the same approach, where you have a lot of SuccessFactors integration
  • Testing synchronize messages, where the Figaf Tool will work as a proxy to give the results back

This function is really useful for SAP PI/PO migrations where you just want to get a lot of messages from your productive system and let contractors handle the configuration. With this approach, they can test all interfaces.

Try it for your self

You can signup for Figaf IRT and get a free trial. You can get started in 20 minutes.