Test case execution

Owned by Kinga Tarczynska
Last updated: May 26, 2021 by Izabela Bogorska (Deactivated)
2 min read

This section will guide you through the single and multiple test cases execution and browsing through the test execution report. You will also learn how test cases for a different types of interfaces are executed. It is worth to mention, that execution of test cases is fully automated.

PROCEDURE:

Typical test execution for most test types (inbound interface test cases) is described below.

  1. Int4 IFTT reads the content of original messages from the test case repository

  2. 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 tracked later on. The system assures integrity by generating unique numbers from the own number ranges that original sender systems would not use.

  3. The Int4 IFTT adapter injects the new messages 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.

  4. Int4 IFTT collects test results. It checks if the results of test cases exist a configured number of times (from the global configuration parameter). If not, it would wait a configured number of seconds (from the global configuration parameter) before the next attempt.

  5. The final automated comparison report is created (see next paragraph). Depending on the test type, it might contain:

    1. Message validation. Current XML or flat file output would be compared with the reference message stored in the test case definition.

    2. 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 test types. Int4 IFTT scans the middleware platform if the expected message is processed. if so, it fetches the content and 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 for different types of integration in the testing concepts section.



© 2017 - 2022 Int4 AG All rights reserved