Would you like to minimize risks of failure on your system when implementing changes?
|Business Test||Developer Test||Mapping Test||Figaf IRT||Tool 1|
|Auto test creation||–||–||–||X||–|
|Test backend functionality||x||–||–||–||R|
|Test all adapters||x||x||x||x||–|
|Test routing of messages||x||–||–||x||–|
|Set up new test cases||+||+++||+++||+++||++|
|Price per test||+||++||++||+++||+++|
|Validation of result||+||++||+||+++||+++|
|Perform complex test||++||++||++||+++||+++|
1) Int4 Regression Interface
R) Receiving Only
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
IRT can connect to multiple agent systems. An agent system could be the productive system or a development system.
- 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.
- 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.
- 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.
- 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.
- The JMS queue is picked up by the test system of IRT.
To perform tests
- You select the ICO you want to use for the testing.
- The user can specify which elements should not be compared using Xpath so e.g. time changes are not counted as errors.
- To test a message the user selects one or more test cases.
- IRT then sends the messages through the XI30 channels it has created, records the output for the message, and makes it the test result.
- After the test is performed, the user will be able to see the result.
Automated recording enabled with a Wizard that guides you thru the process and ensure that you get test messages from all interfaces.
REST-based API: all functions are REST-based. You will get a POSTMan file so you can learn about the different requests, and call the test functions yourself.
Multiple agents: you will be able to test both multiple productive or test systems.
Advanced comparison: compare both dynamic properties and XML messages. Changes in the XML can be ignored.