Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

USE:

The typical process run for test case provisioning includes the following steps:

  1. To create, for example a , an SAP PI/PO inbound test case from a reference document (SAP end to end testing), the tester identifies should identify a middleware message by a specific GUID (Globally Unique Identifier) that which created a final business document (like a sales order). This That can be done with a help of  using a specific GUID (Globally Unique Identifier) of that message and with the help of the Int4 IFTT Message Selector. Together with With the message GUID, the tester must specify the int4 IFTT Automation Object, i.e., containing the common validation rules like, for example, instruction what is on the final document in SAP Backend and how it should be validated. If the Automation Object is empty then , the system will try to determine it by itself by interface message signature.

  2. The int4 Int4 IFTT calls the middleware platform (for example, SAP PO) and retrieves the original input message received by the platform from the sender application.

  3. The original message is stored in the int4 Int4 IFTT database and associated with the final business document number and the business object type.

This simple procedure for creating test cases allows doesn't require the test creator to avoid going go into any sender system to record each test case and . Also, it eliminates the need to create any assertions in the receiver system. However, but it most importantly allows creating hundreds of test cases in a matter of hours which was not possible before.

Info

At this moment, int4 Int4 IFTT support supports users in both manual and automatic test case creation. During manual test case creation, a user needs to provide a message number (using an int4 Int4 IFTT message selector as a guidance) and a previously created automation object. 

Apart from manual creation, int4 IFTT also offers a functionality called called SAP PI/PO Robot. A Robot is a tool which reduce that reduces time spended spent on test case creation to the minimum - it’s . It’s searching for messages on PI/PO based on provided criteria and creates test cases automatically.

This section is divided into two main sections: