Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

This feature is dedicated for to the non-SAP middleware migration to SAP PI/PO.

Table of Contents

Overview

Int4 IFTT Test Case Loader is a functionality thanks to which we can upload test cases into IFTT. This tool supports uploading a single test case (consisting of a pair of input and output payloads) or . It can also be used to mass upload from a folder using a regular expression to match the input/output files.

Each test case added using IFTT TC Loader will be uploaded in in PI Unit Test Test mode (interface type 20) with an input and an output payload. The uploaded test cases can then be then executed to validate the processing in PI (routing, mapping, or modules). To support For supporting the execution of the test case in on the PI system, payloads will be wrapped with a SOAP XI3.0 envelope before being stored into in the IFTT's database. The Loader functionality can be used to, e.g., upload payloads extracted from other middleware into IFTT since it can cater for uploading of XML and flat files.

...

The IFTT Test Case Loader consists of two screens:

  • main screen, where you can fill in all the parameters are filled in before uploading files and creating the test case,

  • result results screen, that displays the summary after executing the Test Case Loader.

...

And each section (A - File Selection, B - IFTT Test Case Details, C - Interface Details, and D - Message Content Type) consists of the following elements (marked in the screenshot above):

A. File Selection

1 & 2

Radio Buttons for selecting single or multiple test case upload mode

3

Input and output file for single test case

4

Folder for multiple test cases

5

Regular A regular expression for matching pairs of input and output files. Two capturing groups are required in the expression:

  1. First The first group for common identifier in both input and output files

  2. Second The second group for the identifier of file type (in or out)

...

C. Interface Details

1

Details of the sender for the XI 3.0 envelope. Mandatory fields are Service, Interface & Namespace.

2

Details of the receiver for the XI 3.0 envelope. Mandatory fields are Service, Interface & Namespace

D. Message Content Type

1

Radio Button for selecting the content type of input message. This setting affects the Content-Type MIME header in the XI 3.0 envelope, ensuring the message triggered from IFTT to PI can be viewed correctly in Message Monitor (XML, Flat File File is the default and only option)

2

Radio Button for selecting the content type of output message (XML, Flat File File is the default and only option)

...

Upon completion of processing, the IFTT Loader results are displayed in an ALV, as shown in below.

...

Result The result screen consists of the following elements

1

Icon An icon indicating the processing status of an individual file

2

Unique identifier of test case pair

3

File The file path of the processed file

4

IFTT Test Case ID created using Loader

5

IFTT payload type added to test case:

  • M – Request (input)

  • R – Response (output)

6

Content counter for responses

7

Error message (if any) during the processing of file

IFTT Test Case Loader use

...

b. Output file (filename: test_case_loader_output.xml):

...

2. The files prepared in the first step should be selected in the section A (File Selection):

...

3. Next, in section B (IFTT Test Case Details), select folder from IFTT Cockpit in which the test case should be saved and Automation Object for the test case:

...

4. Later in section C (Interface Details), fill out the details about the tested interface as follows:

...

5. In section D (Message Content Type), the type for input message and the output message are is set by default as as XML, Flat File, so in . In the next step, click “Execute” the "Execute" button in the top menu:

...

6. Upon completion of processing, the results will be displayed in an ALV, as shown in the example below.

...

7. As we can see in the previous step, the test case was saved with the ID 20008. To verify it, we can go to theIFTT Cockpit (using tcode /int4/iftt_cockpit) and find the created test case:

...

And finally, execute the test case created using the IFTT Test Case Loader:

...

The procedure for multiple test cases uploading mode is the same as for a single test case. The In this case, the only difference is that in this case we should prepare the files with input and output messages in such a way that regular expression (defined in field 5 of section A (File Selection)) would be able to match input and output message for each test case .

...

Info

Please note that you can use any custom regular expression. However, but consequently, the filenames must also be defined according to this expression, so that . Then the TC Loader based on RegEx will be able to identify the message direction (filename containing “in” or “out”"in" or "out") and also a unique test case identifier.

Below you can find steps for an example of using IFTT Test Case Loader to create multiple test cases from a folder with files:

1. First, we need to prepare a folder with files - in this example, we will create 10 test cases by uploading the following files in a folder named “Multiple_Test_Cases_Upload”:

...

As we can see, we will upload 20 files in total , because for each test case, we will upload 2 two files (input and output separately).

2. After proper preparing of files and placing them all in one folder, we select this folder in IFTT Test Case Loader in the section A (File Selection):

...

Other settings (in sections B - IFTT Test Case Details, C - Interface Details, and D - Message Content Type) are the same as in the example for single test case upload, because in this example we are testing the same interface.

3. Next, click “Execute” the "Execute" button, and you will get ALV with results:

...

4. As we can see, all test cases have been correctly created, so we can go to the folder in the IFTT Cockpit where they were saved and execute them:

...