← Figaf Friday

Figaf Friday: why Postman testing for SAP Cloud Integration (CPI) is not enough

Postman is great for sending test messages to SAP Cloud Integration iFlows, but systematic regression testing needs more. What Postman can and cannot do.

July 8, 2022 · 2 min read

We all use Postman to help test our SAP Cloud Integration/CPI. It is a really good tool to use when developing IFlows to see how they react to a given set of data. A lot of scenarios use the HTTP protocol, which makes it really easy to use for the development.

I use Postman a lot to send requests to an IFlow during the development unless I use a scheduled start. Then I have CPIHelper to make it much easier to work with the integration. Because of that, I can see what is going on from just one browser and Postman app.

A lot of people use Postman for testing

I did ask how you performed testing of your SAP CPI and Postman and other tools were the most used on LinkedIn.

LinkedIn poll on testing SAP Cloud Integration: 93% use Postman or another tool, 4% find it too complicated, 1% use Figaf

I obviously hoped to see 25% using Figaf and 50% it was too difficult to test.

I think the part that I missed is something with a systematic test of your integration.

What you can (and can’t) do with Postman

In Postman you can create a set of scripts that will enable you to:

  • Test an IFlow starting with HTTP is working to the end
  • You can set up assertions that you should get some parameters back
  • Insert variables to ensure the message can be processed
  • Share the scripts within your team so everybody will be able to run them

You can perform some advanced scripting in Postman to test your integration, but it will require more of the developers to make sure they know how to create and maintain it. The main part is what the developers need to focus on creating test scripts or create integration.

What you cannot do is:

  • Test integrations using other than HTTP based unless you add a new HTTP endpoint that will be triggered for each execution
  • You cannot mock any APIs for specific cases and make sure they exist in new scenarios
  • It will be extra work to write checks for content from specific payloads used
  • Update the assertions easily each time the result changes
  • Easily record new test cases

If you want to have a more systematic approach to handling your integration testing and create all the test cases, run them and update them as your integration is being developed, the Figaf DevOps Suite makes it easy to create and manage your SAP integration tests.

We talked about how you can perform a better level of organized testing in this week’s webinar about Automating Regression Testing. You can see the replay here. I hope you will check out how Figaf can simplify the way you are working with SAP CPI/Cloud Integration and implement a process of testing all the things needed to run a good DevOps process.

More from Figaf Weekly

Oct 16, 2026

Put your B2B migration on a real calendar

A new calculator plots your B2B migration go-live on a real calendar. Also: wildcard ICO migration, Cloud Integration chamber of horrors and SAP TechEd.

All issues →

See this working in your landscape

No credit card required.

Integration cost calculator →

Start your free trial

No credit card required

Try Figaf DevOps Suite free for 30 days. It takes less than an hour to get started, and we send everything you need by email.

Join our newsletter

Get the latest about Figaf, SAP and anything relevant to SAP integration, every week in Figaf Weekly.