Test Types
In Int4 Suite, a Test Type defines the method and interface through which the system under test is accessed and validated. Test Types allow users to simulate and test different SAP integration scenarios by specifying how messages are captured, replayed, and verified or calling User Interface scripts or external testing software for UI automation.
Each Test Type corresponds to a specific kind of integration technology, such as SAP Cloud Integration, SAP Process Orchestration, IDoc, RFC, SOAP, or OData, and determines how test cases are executed and validated within the Int4 Suite.
The following is a list of all supported Test Types available in Int4 Suite:
SAP PI/PO Testing
PI GUID E2E Inbound
PI GUID E2E Inbound is a test that will inject the message to the SAP PI or SAP PO middleware platform. It can also perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
PI Unit Test
PI Unit Test is a test that will inject the message to the SAP PI or SAP PO middleware platform and it will perform validation of the middleware platform outbound message.
PI IDOC E2E Inbound
PI IDOC E2E Inbound is a test that will inject the message to the SAP PI or SAP PO middleware platform. It can also perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system. The difference between PI IDOC E2E Inbound and PI GUID E2E Inbound is that using PI IDOC E2E Inbound user can create Test Case using IDoc number instead of using SAP PI or PO GUID number.
PI E2E Outbound
PI E2E Outbound is a test that will search for the message in SAP PI/PO middleware platform based on conditions specified in the Variables of Automation Object. It can trigger message by itself via output control or check the outbound message triggered by other test case or manual action.
PI E2E Synchronous
PI E2E Synchronous test type is responsible for testing SAP PI/PO synchronous scenarios. In such cases, test validation is based on a receiver system response message and optionally on the documents created in SAP Backend.
The receiver system will not be virtualized. The connection must be working. The test validation will be performed based on the response from the receiver (after mapping in SAP PI/PO).
SAP Integration Suite Testing
SAP CPI E2E Inbound
SAP CPI E2E Inbound is a test that will inject the message to the SAP CPI middleware platform. It will perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
SAP CPI E2E Outbound
SAP CPI E2E Outbound is a test that will search for the message in SAP CPI middleware platform based on conditions specified in the Variables of Automation Object. It can trigger message by itself via output control or check the outbound message triggered by other test case or manual action.
SAP TPM (B2B) E2E Inbound
SAP TPM (B2B) E2E Inbound is a test that will inject the message to the SAP CPI middleware platform. It will perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
SAP TPM (B2B) Outbound
SAP TPM (B2B) Outbound is a test that will search for the message in SAP IS middleware platform (B2B Monitoring) based on conditions specified in the Variables of Automation Object. It can trigger message by itself via output control or check the outbound message triggered by other test case or manual action.
SAP CPI Subset Unit
SAP CPI Subset Unit Test allows to test a selected fragment (subset) of a Cloud Integration iFlow. This is a special test type, that creates a local, modified and adapted copy of the selected iFlow and tests that copy, providing validation capabilities where typical iFlow start and/or stop points are too complex for straightforward test application.
One of the main principles of testing is to test artifacts/deployments as they are going to be deployed for production. So an ideal scenario is to have the integration flow split into unit-testable iFlows. SAP CPI Subset Unit Test can help when this is not feasible. Please consider, that such test might not capture all the intrinsic feature of the tested iFlow, as a selected subset for testing is carved out, ignoring steps outside the selection.
SAP CPI Subset Unit Test allows to test a selected fragment (subset) of a Cloud Integration iFlow. This is a special test type, that creates a local, modified and adapted copy of the selected iFlow and tests that copy, providing validation capabilities where typical iFlow start and/or stop points are too complex for straightforward test application.
One of the main principles of testing is to test artifacts/deployments as they are going to be deployed for production. So an ideal scenario is to have the integration flow split into unit-testable iFlows. SAP CPI Subset Unit Test can help when this is not feasible. Please consider, that such test might not capture all the intrinsic feature of the tested iFlow, as a selected subset for testing is carved out, ignoring steps outside the selection.
SAP CPI Unit
SAP CPI Unit Test is a test that will integration flow using SAP CPI Simulation capability. It will perform validation of the simulation outbound result. This type of test can be performed on not deployed artifact.
This test type is only available for NEO SAP CPI tenants
SAP Event Mesh Inbound
SAP Event Mesh Inbound is a test that will publish the message to SAP Event Mesh topic or queue.
SAP Event Mesh Outbound
SAP Event Mesh Outbound is a test that will search for the message in SAP Event Mesh platform based on conditions specified in the Variables of Automation Object. It will check the outbound message triggered by other test case or manual action.
SAP Advanced Event Mesh Inbound
SAP Advanced Event Mesh Inbound is a test that will publish the message to SAP Advanced Event Mesh topic or queue.
SAP Advanced Event Mesh Outbound
SAP Advanced Event Mesh Outbound is a test that will listen for messages coming to tested queue or topic and will search for the message based on conditions specified in the Variables of Automation Object. It will check the outbound message triggered by other test case or manual action.
SAP Backend testing types
IDoc Inbound
IDoc Inbound is a test that will inject the message to the SAP backend. It can also perform validation of the database entries created by the message processing in the backend ABAP based system once the IDoc was posted successfully.
IDoc Outbound
IDoc Outbound is a test that will search for the Outbound IDoc message in SAP backend based on conditions specified in the Variables of Automation Object.
It can trigger message by itself by injecting outbound IDoc or via output control or check the outbound IDoc message triggered by other test case or manual action.
Proxy Inbound
Proxy Inbound is a test that will inject the message to the SAP Backend via Proxy Interface. It is used to validate database entries created or modified by the message processing in the backend ABAP based system after it gets injected.
Proxy Outbound
Proxy Outbound is a test that will inject the Message to the SAP Backend via SAP Backend Proxy Interface.
It is used to validate whether logic on the SAP Backend side is working properly and whether specific set of actions generate a relevant Proxy Message.
DB Assertion
DB Assertions is a test that is used to validate database entries on the same SAP backend or on the different SAP backends (e.g. ECC vs. S4/HANA).
File Comparator
File Comparator is a test that will compare two files and will highlight all the differences.
AIF Inbound
AIF Inbound is a test that will inject the message to the SAP AIF on the SAP backend with the SAP AIF XML Application Engine.
It can also perform validation of the database entries created by the message processing in the backend ABAP based system once the SAP AIF XML message was posted successfully.
ABAP Web Service / ICF
ABAP Web Service / ICF is a test type that allows creating test cases based on payloads collected by ICF Recorder for Web Services and REST services based on SAP Internet Communication Framework.
For asynchronous Web Services it is possible to collect the payloads from Web Service Monitor (SRT_MONI) by setting the 'Web Service: Message Monitor Persistency' (WS_PERS_MO) parameter on the Automation Object.
ABAP Web Service / ICF test type is a specialization of Generic Synchronous test type which offers specific way of capturing the request and response.
For test execution all the options and parameters of Generic Synchronous test type apply.
RFC Check
RFC Check is a test that will verify RFC Destinations. It can perform validation of the connectivity, authorizations, logon data and properties like host, port etc.
RFC Call
RFC Call test type allows calling and verifying of results of remote enabled function modules (including BAPIs) on system under test.
With the use of delivered function modules it is also possible to submit report (/INT4/IFTT_F_SUBMIT_REPORT) and call transaction with BDC data (/INT4/IFTT_F_CALL_TCODE) on target system.
File Inbound
File inbound is a test that will upload the file to specified location in SAP Backend via RFC interface.
File Outbound
File Outbound is a test that will read the file from SAP Backend via RFC interface and compare it against stored reference.
User Interface Automated testing
TTA Script
TTA Script test type allows Int4 APITester to call TTA Script that is synchronized with SAP Solution Manager Test Suite. Int4 APITester is calling TTA Script from the Test Suite repository. TTA Script name is provided to Int4 APITester as a document number, thanks to that many TTA Scripts can be handled by single automation object that is not referring to particular flow. If TTA Scripts have differences in input or output parameters, then they need to be called by different, properly adjusted Automation Objects.
Selenium IDE Script
Selenium IDE Script test type allows Int4 APITester to call test scripts created in the Selenium IDE.
Selenium IDE project is saved to local file (*.side) and then imported to Int4 APITester as content of test case of Selenium IDE Script test type.
CBTA Script
CBTA Script test type allows Int4 APITester to call CBTA Script that is created in SAP Solution Manager Test Suite. Int4 APITester is calling CBTA Script from the Test Suite repository. CBTA Script name is provided to Int4 APITester as a document number, thanks to that many CBTA Scripts can be handled by single automation object that is not referring to particular flow. If CBTA Scripts have differences in input or output parameters, then they need to be called by different, properly adjusted Automation Objects.
eCATT Test Script and Test Configuration
eCATT Test Script and Test Configuration test types allows Int4 APITester to call eCATT Script that is created in SAP (ECC or S/4). eCATT Script name or Test configuration is provided to Int4 APITester as a document number, thanks to that many eCATT Scripts can be handled by single automation object that is not referring to particular flow. If eCATT Scripts have differences in input or output parameters, then they need to be called by different, properly adjusted Automation Objects.
Once the eCATT script is executed, Int4 APITester can also validate the backend for correct execution.
Non-SAP Interface Platform Testing
XSLT Transformation
Automation Object XSLT Transformation is used to store XSLT transformation in Int4 Suite as test cases. XSLT Transformation test case can be referred by other Automation Objects or Virtualization Objects. XSLT Transformation test case can store 3 payload types:
XSLT Transformation - contains the transformation that can be referred by other objects
Test Input for XSLT - input for testing XSLT Transformation
Test Output for XSLT - output for testing XSLT Transformation
XSLT Transformation can be Executed in APITester Cockpit. During execution Test Input for XSLT is transform by the XSLT Transformation and the result is checked against Test Output for XSLT. Payload Validation can be applied.
Generic Synchronous Interface Testing
Generic Synchronous is a test type that allows calling HTTP endpoints. It is typically used to test REST or SOAP services and APIs.
Payload for this test type has to be provided manually in the APITester Cockpit.
Boomi Inbound
Boomi Inbound is a test that will inject the message to the Boomi middleware platform. It can also perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
Boomi Outbound
Boomi Outbound is a test that will search for the message in Boomi middleware platform based on conditions specified in the Variables of Automation Object. It can trigger message by itself via output control or check the outbound message triggered by other test case or manual action.
Azure Logic Apps
Azure Logic Apps is a test that will inject the message to the Microsoft Azure Logic App. It will perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
Azure Service Bus
Azure Service Bus is a test that will inject the message to the Microsoft Azure Service Bus queue. It will perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
Payload for this test type has to be manually provided in the APITester Cockpit.
webMethods E2E Inbound Test
webMethods E2E Inbound is a test that will inject the message to the webMethods middleware platform. It can also perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
webMethods E2E Outbound Test
webMethods E2E Outbound is a test that will search for the message in webMethods middleware platform based on conditions specified in the Variables of Automation Object. It can trigger message by itself via output control or check the outbound message triggered by other test case or manual action.
webMethods Unit Test
webMethods Unit is a test that will inject the message to the webMethods middleware platform. It can also perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
MuleSoft E2E Inbound
MuleSoft E2E Inbound is a test that will inject the message to the MuleSoft Anypoint Platform. It can also perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
Solace PubSub+ Inbound
Solace PubSub+ Inbound is a test that will publish the message to Solace PubSub+ topic or queue.
Solace PubSub+ Outbound
Solace PubSub+ Outbound is a test that will listen for messages coming to tested queue or topic and will search for the message based on conditions specified in the Variables of Automation Object. It will check the outbound message triggered by other test case or manual action.