Messages from SAP API Management can be automatically saved as test cases in Int4 IFTT using the Generic Adapter Robot. The Int4 IFTT, Generic Adapter Robot, is functionality that comes to simplify and speed up the test case creation process. There is no need to search messages for a specified interface manually. SAP PI/PO Robot can create test cases based on the existing message Database on Int4 IFTT.
Tcode for the Generic Adapter Robot is /INT4/IFTT_GA_ROBOT.
You can also access the Robot through Int4 IFTT Cockpit under Goto Menu → Generic Adapter Test Case Creation Robot.
Prerequisuites
Suppose you want to take advantage of using automatic test cases creation for SAP API Management. In that case, it is necessary to adjust your Proxy Policies in the SAP API Management. You can find more on how to do this in this section: SAP API Proxy Policies Adjustment
Step-by-step solution:
In Environment Selection, please select the environment from which you want to create test cases:
In the next section, called Message Selection Criteria, you can specify all the needed criteria which should be considered by Robot during message selection.
A mandatory step is a configuration under Open Extended Configuration:
In the beginning, the list will be empty. To import Interfaces from the Database, click on the Import Generic Adapter Interfaces button.
The Robot will search in the message database for interfaces that don't exist on the current list. The Interface list is based on the Interface name, namespace and Integration Platform. All the found results will be populated.
As a next step, we need to specify an automation object for each imported entry.Save the configuration and go back to the main Robot screen.
Next, you should select a period for which Robot should search messages on the Database.
In the example, the Robot will search for messages in the past 24 hours.
You can also restrict the search by adding additional criteria in IFTT Automation Object, Interface name, and namespace or providing the name of the Subfolder specified in the Extended Configuration.
Now we move on to the Message Search Control Parameters, where you have to define the maximum number of test cases that will be read from the Database for each Automation Object.
In the next section you can specify Execution Parameters:
Test Run - Robot will search for messages and list out the results without creating any test cases.
Log Level - Debug - you can select this option to obtain log messages during execution.
The last section covers information about Test Case Creation Parameters.
Firstly, specify Target Folder where test cases created by Robot should be located (use the F4 input help if needed).
Suppose you didn’t specify Automation Object ID in Extended Configuration or given object won’t be found by Robot. In that case, you can select a checkbox to force the creation of an automation object during execution (checkbox Create Automation Objects if ID from Extended Configuration is missing).
Define rules about Test Case folders in case folder was not maintained in Extended Configuration. You can ask Robot to search for an existing folder or create a new one using a search pattern. For more information about possible Search Patterns, please open the F1 help.
Enter additional data:
maximum number of test cases per folder (including already existing ones),
select Skip duplicates in the same folder in case you don’t want to have more that 1 test case with the same Message ID,
Randomize message selection - if there is a bigger number of messages in PI/PO, for example 200, you can select this option to pick up messages randomly instead of picking 10 messages in a row.
define Interface Types for Test Cases - in our case it’s 54 (Generic Synchronous).
at the end, fill new test case name pattern for test cases created by robot (you can also use here the F1 help for more information).
After you specify all the criteria, execute the report.
After the execution you will find a screen with additional information:
Robot automatically fetched messages from the Database and creates the folders if needed with test cases based on criteria from selection screen. You can find a summary at the end of the list. When you open Int4 IFTT Cockpit (tcode /INT4/IFTT_COCKPIT), you should find test cases in the specified folder with the additional subfolders.
