Testing via Send Message using FIGAF

FIGAF is a software company that specializes in automating and simplifying SAP Integration processes, including migration, testing, DevOps, and transport management. It provides tools that help organizations move from SAP Process Integration (PI/PO) to SAP Integration Suite with less manual effort and fewer errors.  

I have been using FIGAF in a project recently for a SAP PI/PO to SAP Integration Suite migration and would like to show how easy and beneficial testing can go via FIGAF. 

Some of the key advantages of iFlow Testing via FIGAF include: 

• Automated Test Case Creation & Execution 

• Regression & Baseline Testing 

• Chain & Pipeline Testing 

• Migration Support (SAP PI/PO → SAP Cloud Integration) 

• Non-Intrusive Testing Process 

• Automation & Scheduling 

While there are a few different ways to test your SAP Integration Suite iFlows via FIGAF, and there is so much more detail I could go into, I would like to focus on sending and saving test messages via their Testing Tool à Send Message.  

To send a test message, you will go to Testing Tool à Send Message and select the appropriate Agent (SAP system) that the test will be sent to. From here, you can go ahead and Create Request. 

In Request Details, I personally find it easiest to first select the Integration Object that you are looking to test – this will display information about all imported iFlows. You have the option to filter through different categories, such as the Type, Package, Technical Name, Displayed Name, and Version – I personally like to filter via Displayed Name:

Once you find and select your Integration Object, the required URL and Adapter Type will be filled automatically. For the Name, I enter here the Displayed Name (my iFlow name) that was selected in the Integration Object. For the Collection, I enter the name that I would like to organize and later identify this test. Since I’m testing many iFlows found in different packages, I’ll enter here the Package name where I can find the given iFlow:

Under Request Headers, you can enter any HTTP request headers that you might want to send along with your test file.

You will copy and paste your test file into the Request Body, and enter the corresponding Content Type:

You then have a few options to send the test file over your iFlow:

1.        You can Run, which will send the test file over the selected iFlow in SAP Integration Suite and provide you with immediate information from Monitoring about the results of the test:  

You can find even more information about the test by selecting Open Figaf Message Browser in your result. Here, you will see the individual steps that your test went through, for example, if you are using a Pipeline, and you see the results from the SAP Integration Suite Monitoring. From here, you can click around and discover even more details about the specific Integration Object, information about the creation and versions, documentation and shared resources, linked objects, etc. You really have the best possible overview for your test cases, making it easier to detect and correct the errors.

2.        You can Run for Recording, which will switch the iFlow into ‘Trace’ mode and enable the test file to be sent to the specific endpoint. Once the test file is recorded, you can add it to a new or existing Test Suite, where it is also saved for further testing purposes under Test Suites.

Regardless of which testing option you choose, you can Save your test case. This will make the Request available directly in Send Message under the Collection entered:

This function is actually really interesting and useful, as you can go back to that exact test and it’ll even save the test file that you used to test the iFlow. Now, you would be able to make the corrections to your iFlow and simply Re-Run or Re-Record. You wouldn’t need to fill in the Request Details again and find a new test file, you can simply reuse it. Of course, you do also have the ability to test with other test files - it is important to test different scenarios when creating iFlows.

If anything should change to this saved Request, you also have the ability to Edit here.

In conclusion, FIGAF provides many useful ways to test your iFlows, resulting in faster deliveries, fewer errors, and greater confidence in your SAP Integrations. I just briefly touched on one way of testing via FIGAF, but there is so much that FIGAF has to offer for your SAP migrations.

Want to know more? Feel free to contact us

Cover designed by Freepik