How to create a Test Case

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

To create, for example, an SAP PI/PO inbound test case from a reference document, the tester should identify a middleware message which created a business document (like a sales order). That can be done using a specific GUID (Globally Unique Identifier) of that message and with the help of the Int4 IFTT Message Selector. With the message GUID, the tester must specify the Automation Object, containing the validation rules like, for example, instruction on the final document in SAP Backend and how it should be validated. If the Automation Object is empty, the system will try to determine it by interface message signature.
The Int4 IFTT calls the middleware platform (for example, SAP PO) and retrieves the original input message received by the platform from the sender application.
The original message is stored in the Int4 IFTT database and associated with the final business document number and the business object type.

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

At this moment, Int4 IFTT 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 IFTT message selector as guidance) and a previously created automation object.

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

If you would like to read more about the test case creation, check the material corresponding to your needs: