...
For more info on how to fill this section, check Automation Object Definition.
2. Go to Variables and define Variable name and Variable description. You can declare an unlimited number of variables.
...
Define also Variable processing. Please note that the PO number is being read from the parent test case. In the case of a one-to-many relationship between "parent" and "child" test cases (as it is in this example), we should use a variable processor named "READ_PREVX" together with the Action "Populate variable before execution" and proper Processing Parameter value. Combining these parameters (first record on the screenshot below) is used to filter the comparison between the new messages with their respective reference messages. Filtering is done using values taken from the message based on the path entered in the field Processing Parameter). In this example, we compare IDOCs, defining XPath to the segment that contains the purchase order number: //E1EDK01/BELNR/text().
...
3. Optionally, we can define define Payload Validation Ignore List, i.e., fields that should not be compared during verification between reference and current message. As an example, a difference in the generated document number or the date can be used here. For more info on how to use this section check , check the Payload Validation Ignore List.
...
After creating and defining Automation Object, create and save the IFTT test case (provide . Provide Test case description, Interface Typeas as PI E2E Outbound, Automation Object created above and select reference messages for mentioned Interfaceinterface). To make sure that we get the right messages while crating “child” "child" test cases, we can select the parent test case and click the “Content” "Content" button to see the input message as shown below:
...
There we can see the input for the test case:
...
And we can notice that for the “child” test case’s For the "child" test cases, we should select (using the the IFTT message selector) three messages containing purchase order numbers marked on the screenshot above (in . In this example: , the values are DD05847, DD05848, and DD05849) .
Please remember to choose the number of the previous test case as Parent ID before saving “child” test cases:
...
Select all created test cases (from Part A and B) and click the “Execute Selected” button:
...
For details of each test case, click on the given test case (below is a report for a test case where the reference PO reference value is DD05847).
...