Page Comparison

The The PO Unit Test type  type requires the a minimal level of parameters to start test automation.

Since Int4 IFTT 1.0 SP11 release 005 automation object creation is available in in SAP PI/PO Wizard.

Below procedure describes manual The below procedure describes the manual creation of the automation object for a new interface to be tested. 

Step-by-step guide

1. Analyze the integration flow to be tested and find processed messages that might be used as test case data.
   1. check if Check if staging/ logging logging levels are enough.  
      1. In this step, you need to check if your interface operates on XML or flat files or there are Adapter Modules that you also would like to test (both on the input and output side). If so, then the SAP standard MessageLoggerBean standard MessageLoggerBean module should be added in to the communication channel that will log the payload before or after processing of those adapter modules. Currently, testing of flat content conversion is available only if is done by Adapter Modules do it. 
   2. Find a few few valid messages processed by the interface. They must be correct both from the technical and functional point points of fewview. The messages will be used to test your automation object and to create the first test cases. This step is also possible when the automation object is created by when Int4 IFTT Message Selector creates the automation object. 

1. Run /INT4/IFTT_CONF and create a new entry for the tested interface or use SAP PI/PO Wizard 
2. Specify:
   1. IFTT Object definition -  a name of automation object that will be used later in test case creation. May contain your internal number of interface interfaces from the interface master list.
   2. Automation object description
   3. Service Interface Name - Sender Interface Name from Integrated Configuration (ICO) or Receiver Determination Object
   4. Service Interface Namespace- Sender Interface Namespace from Integrated Configuration (ICO) or Receiver Determination Object
   5. Default Interface Type- choose from list value: 20 20 (PI Unit Test). This setting would allow to find finding this particular object definition when two definitions will exist for the same tested interface (ex. one for end-to-end testing, second for PO Unit testing)
   6. alternatively activate Alternatively, activate Debug- this option will display additional messages and information during the execution of the first test cases. It would also allow to add adding exceptions for differences directly from results. Later it can be deactivated after confirming the that the object works correctly.
3. Create your first test case and validate the configuration. Please refer to to the test case creation section and its subsections.

The above steps are mandatory, and in most cases, your interface is almost ready to be tested. However, there is also a set of additional settings required in particular business scenarios.

1. Set the Additional Parameters to fetch the correct version of messages from SAP PO persistence. Please note that a single interface could have multiple receivers with different persistence settings. This situation may occur when there is a an additional custom additional logging as an adapter module in the communication channel. In such a case, multiple parameters can be populated using the grouping field. (parameters parameters Message version before processing and and Message version after processing)
2. Set the Additional Parameters for processing flat messages
3. Set the Additional Parameters forcancelling canceling messages after processing to to prevent sending out messages to real actual receivers
4. Set thethe Payload Validation Ignore list  to  to add all the the fields or nodes that may be different differ in the outputs and but should not fail the test case. In Debug mode, the Ignore list exceptions might be added directly from the XML comparison result comparison result screen. 

In most cases, The same input messages will be injected to into SAP PI/PO during the testing in most cases.   Alternatively using , using variables, variable processors and , and number ranges, the input messages can be changed before processing. 

...