Figaf Testing Tool

Know what a change broke, before it reaches production

Test your SAP integrations with the messages your production system already handled, without scripting test cases and without the endpoints being live.

Start free trial Part of Figaf DevOps Suite

A test request in Figaf, sent to an iFlow on SAP Cloud Integration, with the response status and body shown beside it

Increase the quality of your releases

Validate your system after a change, to make sure everything works as expected. If you test all integrations before going live, you deliver integrations of higher quality, with fewer errors.

Testing changes is about peace of mind: knowing the system will keep working after a change, without unexpected errors in other parts of the interface. We have found that the best approach to SAP integration testing is to fetch messages from the production system and use them as the baseline for testing.

Avoid unexpected changes in the interface
Perform tests quickly and reliably
Test without deep knowledge of the integration

Use production data as the basis for testing
Test confidential data securely
Support all types of integration

The Figaf Testing Tool is part of the Figaf DevOps Suite, which brings together all the tools you need to manage and automate SAP integration.

How Figaf tests your integrations

Open a topic to see how it works and what it looks like in a real landscape.

Many test casesUse production messages, with all their variations, as your test cases.

There is a lot of logic in your SAP integrations. Sometimes it is simple; sometimes there are complicated rules for how lines are handled. A standard test case tests one item, but in real life customers place complex orders, and that variety is hard to create by hand. That is why it makes sense to use production data as the basis for testing.

In practice: Foodstuffs South Island retrieved test cases from their production environment to test their migrated iFlows, so the test data was like for like.

Simple test case creationCreate test cases without deep knowledge of the integration.

You can create test cases with limited knowledge of the integration. That makes test data much easier to create, and lets you keep testing even when the key developers or consultants have left the project.

In practice: A developer changes a mapping on Friday afternoon and knows within a minute whether the other fourteen fields still land correctly. Read more →

Support all your integrationsEDI, modules, bridges and other common patterns, without programming.

Whatever you use in your SAP PI/PO or Cloud Integration project, the Figaf Testing Tool can handle the test case for it, without any programming: EDI comparison, the output of your modules, bridges such as the async-sync pattern, EDI separators and other common patterns.

In practice: During Medela’s migration, test cases recorded in SAP PO were compared with the migrated flows at several points, including the raw X12 EDI and its conversion to EDI-XML, which caught most conversion errors early.

Secure test dataTest with production data, without exposing what is confidential.

If you use production data for testing, you need to protect it. It could be payroll or financial payments, subject to GDPR or SOX rules. Figaf has different ways of keeping that data safe, so contractors can run your test cases without seeing the confidential content, and everything can still be tested according to your requirements.

Mocking of servicesTest complete flows, even when the systems you call cannot repeat a call.

When you test complete flows, the web services you call often will not accept the same call twice. Call SuccessFactors to hire an employee, and the next call fails because the employee already exists. Figaf automatically mocks the services you need to run the test.

In practice: Running the nightly regression suite at 02:00, when the partner's system is down for maintenance. Read more →

Unit testing for scriptsReuse your test cases to test your Groovy scripts.

Reuse your test cases to create test scripts for your SAP Cloud Integration Groovy scripts. It makes it much easier for developers to run and validate the changes they make.