Messages from SAP API Management can be automatically saved as test cases in Int4 Suite using the Generic Adapter Robot. The Int4 Suite, 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. The Robot can create test cases based on the existing message Database on Int4 Suite.
...
In Environment Selection, please select the environment from which you want to create test cases:
In the next section, called Payload Selection, 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. TO DO - not working
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 Int4 Suite 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. Here you have to define the maximum number of test cases 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 Robot won't find a given object. 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 than one test case with the same MessageID,
Randomize message selection Suppose there is a bigger number of messages in the system, for example, 200. In that case, you can select this option to pick up messages randomly instead of picking ten messages in a row.
Define Interface Types for Test Cases - in our case, it will be 54 (Generic Synchronous).
In the end, fill the new test case name pattern for test cases created by Robot (you can also use the F1 help for more information).
After you specify all the criteria, execute the report.
...