You cannot tell what a change broke until someone downstream complains.
Testing SAP integrations normally means writing scripts that go stale, or clicking through the flow by hand and hoping you remember what “correct” looked like. Figaf regression testing builds the test case from traffic your landscape already produced, so integration developers, testers and migration teams can rerun it on every change and see what came out differently.
How it works
Figaf uses record and replay. You pick messages that already ran, and they become the baseline: the input message and the expected output. When the flow changes, Figaf runs the same messages again and compares the new output with the expected one.
Record from production data. Fetch messages from the production system, with all their variations, and use them as test cases on development or test. You can select many interfaces at the same time, and set up a hundred test cases for an ICO in the time it takes to collect the test data.
SAP Cloud Integration. Figaf uses the trace functionality, so you can record without modifying the iFlows. HTTP, SOAP, ProcessDirect, IDoc, JMS and XI 3.0 senders are supported, and for other adapters such as SFTP Figaf creates a copy of the iFlow with an HTTP endpoint. Test cases can span several iFlows connected through ProcessDirect or JMS, and you can include or exclude specific steps.
SAP PI/PO. Figaf reads the payloads from the message logs, so nothing has to be installed on the PI server. The interface must log both the inbound and outbound message. When you record, Figaf shows if the logging settings could cause problems. On a dual stack system, Figaf can record through your Integration Suite system as a proxy to the RFC.
B2B and TPM. Test cases can be created from the data in TPM agreements, so you search across the agreement parameters to find the test cases to run. This works with MIGs and MAGs and with iFlows using ProcessDirect, and does not require trace mode, which makes it possible to test at the scale of the landscape. EDI comparison handles X12 and EDIFACT.
API Management and events. The same recording and comparison covers SAP API Management proxies and Event Mesh.
Comparison and ignore expressions. Ignore expressions (XPath for XML) hide differences that do not matter, such as a missing element that equals an empty one or a different number of decimals, so the real differences stand out. A text diff view is also available.
Run only what a change affects. Figaf sees which interfaces have been updated and runs the test cases for those, instead of every test case. You can also run only selected test cases in a test suite.
Maintain test cases. When a mapping changes on purpose, you update the test case to use the current output as the new expected result, instead of recording it again. Figaf shows when a test case was created and last updated, and from which versions.
Ignore expressions keep the focus on the differences that matterB2B test cases connected to the data in TPM agreements
Business value
Fewer surprises in production. Every change can be tested against real messages before it is transported, so unexpected changes in other parts of the interface are caught early.
Less dependence on individual specialists. Because the test case comes from real traffic rather than written by hand, it needs limited knowledge of the integration to create and maintain. That matters when the consultant who built the flow has moved on.
Less time spent on testing. No test scripts to program, and only the affected interfaces are run. Test cases from a migration can be reused for regression testing afterward.
Safer handling of confidential data. Data from production can be marked as sensitive and shown masked, so contractors can run test cases on payroll or payment flows without seeing the content, in line with rules such as GDPR or SOX.
Evidence for audits and sign-off. A testing result can be downloaded with the testing report, input messages, expected output and actual output, so you can keep the test record in an external tool. In a migration, you sign off an interface because the output is identical, not because it did not throw an error.
Good to know
Regression testing is part of the Figaf DevOps Suite and the Figaf Testing Tool. In the Figaf Migration Tool, test cases recorded on SAP PI/PO can be run on the migrated iFlows.
Figaf has been able to test SAP PI/PO since 2016.
Figaf can start expecting messages through its API, which lets you extend test cases in tools such as Tricentis to check the SAP integration flow they trigger, correlated by document number.
