Test Cases are the basic, smallest units of work available in Int4 Suite.
Building
...
Blocks of a
...
Test Case
Each 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 |
Assignment | Controls the test case execution, data processing |
and test case validation. For reference, see the following manual section: Automation Objects |
Test Type |
Test Case is always defined with a type. It |
specifies the test case execution technology and logic (e.g. Inbound or Outbound, webMethods or SAP IS) |
Reference |
Document Number | Links the test case to a reference document or execution object (e.g., ID for integration platforms or UI scripts). 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 |
Test Payloads | This is the actual testing data |
used for test execution and validation. |
Test Payloads
...
Test Payloads can may 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 , provided a Reference Document number Number is providedspecified.
For Integration Platform integration platform Inbound test types, Int4 Suite will capture at least two Payloads.
The Payload that That enters the integration platform
The Payload that That integration platform generated as the output of the processing. Due to the complexity of some interfaces, integration platform can may generate multiple outputs from a single input. In such a scenario multiple outputs will be are captured
For Outbound test types and some Inbound test types not related to integration platform (e.g. IDoc processing) Int4 Suite captures only one Payload.
| Info |
|---|
For non-interface test types, like such as Selenium or eCATT the test Payload is not used directly. For such test cases Payload is either needed required for test case execution, or has a special meaningpurpose. Specifically, for Selenium testing, the test script should must be loaded uploaded as test case Payload. |
Test Payloads
...
Structure
Integration Platforms often process more than just the actual Payload. The Payload can may be accompanied with an envelope or a technical header that controls the Payload its processing by the Integration Platform. To enable testing of such scenarios, Int4 Suite captures both the Payload and the accompanying metadata, referred to as the Payload Header. For Integration Platforms where the If header data is not accessible, Int4 Suite will create a Payload Header Payload with basic metadata, to enable consistent processing.
| Info |
|---|
Note that data operations in Variable processing, can may be specified to work on the business Payload and/or on the Payload Header. |
Test
...
Case Execution Steps
| Info |
|---|
Please note Note that these are generic general test execution steps. The actual details can vary depending on test technology, and more further 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 |