Would you like to minimize risks of failure on your system when implementing changes?

The Figaf Integration Regression Tool enables you to test your SAP PI/PO interfaces faster. IRT is the only tool to make a generic way to test all interfaces no matter which adapter is used. A wizard will guide you thru getting test data from your productive system, so you get real data. You can then run the test on your QA system. IRT will perform automatic comparison of the resulting documents.

You can run the test every time a mapping is changes or a support pack is installed. You will save hours of testing and ensure fewer error in your productive system.

How it works

How simple is it?

Record live messages

Simple way of saving live messages and their output for test cases

Set up test scenarios

Use your existing ICOs to run the tests

Run tests

Running regression tests with the recorded message on the test system


Verifying that the original messages correspond to the test run

It has always seemed nearly impossible to create any good tests for the SAP XI/PI/PO/PRO system. There were missing features that allowed the developer to test, but only if the expected things changed.
Problems could arise when there was a change to a message mapping, UDF, or even when applying a support package. The normal way of conducting a test is to send a few messages through the system with the help of the business or the developers. This is mostly a ‘pray and hope it does not break anything’ procedure. It is not something that coincides with the way most SAP companies want to operate.
Other development factories use test-driven approaches to make sure no bugs are introduced. This is the problem the Integration Regression Tool solves.
IRT is the only tool that allows you to test your mappings, modules, and routing.

How it works

Recording messages

IRT can connect to multiple agent systems. An agent system could be the productive system or a development system.
  1. To be able to record messages in the modules, IRT adds a module as the first module on the Sender communication channel and last on the Receiver Communication channel. This is the Agent Module.
  2. When the user from IRT wants to record a number of productive messages, IRT sends a command to a web service on the agent system, along with the information that the specific interface should record the next e.g. 5 messages.
  3. The Agent Module will then verify if the message coming through should be saved, and if it should be saved, it saves the message to the JMS queue. It also marks the message to be saved by adding a dynamic property to the message.
  4. When the messages receive the Receiver Agent Module, the file is saved again as the result of the message. There can be multiple outputs of an input message.
  5. The JMS queue is picked up by the test system of IRT.

To perform tests

  1. You select the ICO you want to use for the testing.
  2. The user can specify which elements should not be compared using Xpath so e.g. time changes are not counted as errors.
  3. To test a message the user selects one or more test cases.
  4. IRT then sends the messages through the XI30 channels it has created, records the output for the message, and makes it the test result.
  5. After the test is performed, the user will be able to see the result.

How IRT works