SAP Process Integration Test Tool (PIT) – News in SP15
In this blog, we will share with you the new functionalities of the PIT Tool in SAP NetWeaver 7.50 SP15.
To configure a Test Run you need to create a new configuration. This needs the following information: the Test Case, the Data Set, the Target System and the Target Configuration Object. So far, you had to create a configuration from the Run menu. With SP15, you have three further options to launch a configuration which help to get all the information prefilled.
Launch Configuration from the Test Case Browser
Launch Configuration from the Test Case Configuration Object
Launch Configuration from the Test Case Data Set.
For each option, all known information is prefilled in the configuration.
Also a name is automatically generated based on the Test Case name or the Test Case and the Test Dataset Name, depending from where you launched the configuration.
You can now save and reuse this configuration – or run it without saving.
As usual you will see the run in the Job Browser.
Enhancements in the Verification UI
With SP15, we have completely reworked the verification UI. It is possible to see the whole message exchange from the sources and the target message in the Verification UI.
The overview page is still the same. It shows the overall number of messages processed, the number of failed messages as well as the number of differences if any.
You can click on the links to context-sensitively navigate to the other tabs within the verification UI.
Or simply select the tabs to switch to the same. On the Message Overview tab, you see all messages including their execution and verification status. In case of differences, the number of differences are shown.
Switch to tab Error Overview, if you like to get an overview about what kind of errors occured. In the lower screen, you can switch to the Test Verification Problems tab to get more details about the differences.
If you have worked with the previous version of the PIT tool, you will notice that the actual comparison screen has been completely changed. Switch to the Exchange Structure Overview tab to browse through the differences. On the new page, a split window shows the source and the target message exchange. If the messages differ in the content, by default the compare mode is used. In this mode, both windows work synchronously, e.g., if you select the Payload of the outgoing message in the source, the target automatically switches to the respective Payload as well. You can turn off this mode if you like to compare different exchange structures with each other, e.g., you may like to compare the incoming message payload of the source with the outgoing message payload in the target.
The following content differences are supported: differences in the payload, the attachments, the message header, and the dynamic header.
The payload difference is high lighted. It is possible to navigate from one error to the next.
Binary content cannot be shown in the UI – but you get the error message in the Test Verification Problem view.
In case of structural differences, it is not possible to use the compare mode. So, the compare mode is automatically switched off. The navigation has to be done in each window separately. Structural differences can either happened within a message …
… or due to missing messages.
This data set has messages with verification differences and some without.
Comparing the messages indicate that a wrong code page has been.
After having fixed the code page issue, the messages are successfully processed.
In case that on the source and the target system the configuration differs in either the Communication Component, Communication Party, Interface Name, or Interface Namespace it is possible to create replacement rules. With those rules in place, the verification ignores any of those differences.
In order to define a replacement rule, open your test case, switch to the Verification tab, and add a new rule for the structure comparator. In the upcoming dialog, select the type of structure object.
In our example we like to create a rule for the interface name
Here we go:
More information about the SAP Process Integration Test Tool can be found in the SAP Online Help