In this This section we will guide you through the single and multiple test the single and multiple test cases execution and browsing through the through the test execution report. You will also learn how test cases for a different type types of interfaces are executed. It is worth to mention, that execution of test cases is fully automated.
PROCEDURE:
A typical Typical test execution for most of test types (inbound interface test cases) is described below.
int4 Int4 IFTT reads the content of original messages from the test case repository
if If there is such configuration in its Automation Objects, the messages are enriched. For example, the original business document identifiers are replaced with the new numbers that will be tracked later on. The system assures the integrity by generating a unique numbers from the own number ranges , that would not used by original sender systems would not use.
The Int4 IFTT adapter injects the new messages are injected by the int4 IFTT adapter to the integration platform or SAP Backend (service virtualization). From that point, the integration platform processing and further actions are not affected by Int4 IFTT.
Int4 IFTT collects test results. Number It checks if the results of test cases exist a configured number of times (from the global configuration parameter), it checks if the results of test cases exist. If not, it would wait a configured number of seconds (from the global configuration parameter) before the next attempt.
The final automated comparison report is created (see next paragraph). Depending of on the test type, it might contain:
Message validation. Current XML or flat file output would be compared with the reference message stored in the test case definition.
Document comparison in SAP Backend. Thanks to the automation object database rules, Int4 IFTT extracts the tables and fields from the SAP database and compares the current document created by the interface posting with the reference identified based on test case data.
The execution process for other test types might look different. For example:
outbound Outbound test types. Int4 IFTT scans the middleware platform if the expected message is processed. if so, it fetches the content and perform performs the comparison with the reference data
SAP eCATT test type. Int4 IFTT will trigger the SAP eCATT test configuration and waits for the execution.
You can find more information on how the test case execution works in for different types of interfaces integration in the testing concepts section.