In this section is presented an overview of the mandatory elements for the use of Int4 IFTT on a non-SAP middleware platform. Before the regression testing starts there are several elements that Int4 IFTT requires in order to create and execute test cases. As you can see on the diagram below, the testing is separated on two parts. So lets have a look on the details of each part, in order to make clear what exact steps are performed.
Before Testing
Think of any process, it has a connector in order to receive input messages. Then the process logic manipulates the input message according to the requirements. Finally, at the end of your process there is another connector thet sends the messages to SAP ECC or S/4HANA system.
In order to perform regression testing and validate the process logic we need to take an already successfully processed input message, re-run it and compare the outputs.
For that purpose, before testing, Int4 IFTT needs to receive both, input and output, message payloads.
Technical Preparation Steps
As shown on the diagram, Int4 IFTT requires the logging of payloads before processing (exactly after the start connector) and after the processing logic (before the send connector).
In many cases the payload logging is already implemented on the original processes. In that case the current common logic for logging can be reused, and just in the logging process needs to be done a modification, in order to call a Payload Persistence Process that will save the payload to Int4 IFTT.
Otherwise, when there is no logging mechanism on your processes, the persistence for payloads needs to be provided by changing the original processes.
The Testing
During test case execution Int4 IFTT is able to inject the input message into the correct Dell Boomi process. This is handled by an additional process called Int4 IFTT Dispatcher. After the message enters to the original process, it get processed as usual. At this step we will also need the payloads before and after processing. In the same way like before testing, the message payloads are going to be stored in Int4 IFTT and will get compared accordingly. Finally, you end up with the Int4 IFTT Test Results Report.
Technical Preparation Steps
To achieve the injection of the input messages into the corresponding process, an additional process called Int4 IFTT Dispatcher is required. The Dispatcher is a process which allows to virtualize the sender systems be sending the messages to the original processes.
Inside the Dispatcher there need to be configured a corresponding routing logic for the processes that s going to be tested. In order to complete the Dispatcher routing, Int4 IFTT provides additional details on HTTP custom headers together with the input message, so the Dispatcher knows which process need to be called.