Test Cases
Test Cases are the basic, smallest units of work available in Int4 Suite.
Building blocks of a test case
Test case consists of several data elements and settings, which are processed by Int4 Suite test execution engine. Some of these settings are captured under the Automation Object - this allows re-use and sharing of testing configuration between multiple test cases.
Test Case element | Purpose |
|---|---|
Automation Object reference | Automation Object contains general setting regarding test case execution, data processing (using Variables) and test case validation. |
Test Type reference | Test Case is always defined with a type. It defines the test case execution technology and logic (e.g. Inbound or Outbound, webMethods or SAP IS) |
Reference document number | At the time of test case creation, it is possible to specify the reference document name or execution object. For integration platforms test, this usually maps to an unique ID of the document used for test case creation. For UI testing types, this will refer to the identificator of the UI script to be executed. For details about the actual application of this field, please refer to the specific Automation Object test type definition in this manual. |
Test Payloads | This is the actual testing data to be used for test execution and validation. |
Test Payloads details
Test Payloads can be entered manually. Most often, Test Payload is captured from the Integration Platform or from the tested system (e.g. from S/4HANA IDocs) at the moment of test case creation. Int4 Suite attempts to fetch test case data from the reference system at the moment of test case creation if a Reference Document number is provided.
For Integration Platform Inbound test types, Int4 Suite will capture at least two Payloads.
The Payload that enters the integration platform
The Payload that integration platform generated as the output of the processing. Due to complexity of some interfaces, integration platform can generate multiple outputs from a single input. In such a scenario multiple outputs will be captured
For Outbound test types and some Inbound test types (e.g. IDoc processing) Int4 Suite captures only one Payload.
For non-interface test types, like Selenium or eCATT the test Payload is not used directly. For such test cases Payload is either needed for test case execution, or has a special meaning. Specifically, for Selenium testing, the test script should be loaded as test case Payload.
Test Payloads structure
Integration Platforms often process more than just the actual Payload. The Payload can be accompanied with an envelope or a technical header that controls the Payload processing by the Integration Platform. To enable testing of such scenarios, Int4 Suite captures both the Payload and the accompanying metadata, as the Payload Header. For Integration Platforms where the header data is not accessible, Int4 Suite will create a Header Payload with basic metadata, to enable consistent processing.
Note that data operations in Variable processing, can be specified to work on the business Payload and/or on the Header.
Test case execution steps
Please note that these are generic test execution steps. The actual details can vary depending on test technology, and more details can be found the in the description of Automation Object settings.
Inbound and Unit-testing test types
Execution step | Details |
|---|---|
Data pre-processing | Test case Payload is loaded, and processed according to Variable definition in the relevant Automation Object. All relevant Variables are updated. |
Inbound message send | Test case data is sent to the integration platform interface, depending on test type and Automation Object interface specification |
Outbound message capture | Int4 Suite is polling integration platform to find the relevant results of message processing |
Outbound message validation | Int4 Suite validates the captured outbound message, by comparison with the test case payload data. Payload validation ignore rules are checked. |
Variable processing | According to definition in the Automation Object, Variable processing is applied to capture data from the outbound message |
Database Validation | If the Database Validation data was defined in the Automation Object, Int4 APITester will proceed with Database Validation steps. Also, Variable references will be updated, to capture data read from the Database |
Outbound test types
Execution step | Details |
|---|---|
Data pre-processing | All relevant Variables are updated. |
Outbound message capture | Int4 Suite is polling integration platform to find the relevant results of message processing. This requires a “Find” definition for Variable processing |
Outbound message validation | Int4 Suite validates the captured outbound message, by comparison with the test case payload data. Payload validation ignore rules are checked. |
Variable processing | According to definition in the Automation Object, Variable processing is applied to capture data from the outbound message |
Database Validation | If the Database Validation data was defined in the Automation Object, Int4 APITester will proceed with Database Validation steps. Also, Variable references will be updated, to capture data read from the Database |
Other test types (for example - UI testing)
Execution step | Details |
|---|---|
Data pre-processing | All relevant Variables are updated. |
Test execution | Execution of the test, according to defined test type |
Variable processing | According to definition in the Automation Object, Variable processing is applied to capture data from the test execution message |
Database Validation | If the Database Validation data was defined in the Automation Object, Int4 APITester will proceed with Database Validation steps. Also, Variable references will be updated, to capture data read from the Database |
© 2017 - 2022 Int4 AG All rights reserved