Automation Objects contain configuration for each test execution. Automation Objects define the interface under test, test conditions, and necessary data manipulation. Automation Objects can also point to other objects, UI scripts, database validation definitions, and more.
Automation Objects Management
...
Clicking an Automation Object from the list or creating a new one will open Automation Object edition screen.
...
Video guide for Automation Object creation
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Automation Object edit screen sections
First items from top are the automation object name, description and assigned test type. Then the screen is divided in several sections. Navigation between these sections is possible by scrolling or clicking the section names.
...
This section contains the basic information about the integration being tested. Depending on selected test type this section will contain different fields, relating to the specific integration technology - e.g. for SAP IS (CPI) these would be the iFlow name.
Backend Systems
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This feature is available only in APITester |
...
Backend Systems allows to specify the system lines for database validation. The specified systems lines are read from the configuration and, together with landscape on which the test case is executed, map to a RFC connection. Int4 Suite uses this RFC connection to execute dedicated function modules and reading data from the system’s database for comparison.
...
| Info |
|---|
Based on Your testing scenario, both current and reference system lines can be the same or different. For regression testing it will usually be the same system line, e.g. ECC. The testing landscapes are then different, e.g. Test and Production and the system would read reference from Production and current document from Test. For migration scenarios, e.g. ECC to S/4HANA, usually the reference would be ECC and current would be S/4HANA. Please refer to the https://int4support.atlassian.net/wiki/spaces/IUM/pages/2068021270/Int4+APITester#Environments-and-System-lines section for more details on the system lines definition. |
Database Validations
[this is only available in APITester]
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This feature is available only in APITester |
...
Database Validation ruleset points to a specific Database Validation object. It’s Its settings are read and used for execution of the database tables and fields comparison. This allows for single database validation ruleset to be used with multiple Automation Objects.
| Info |
|---|
Read more here on defining the Database Validation rulesets: DB Validation Rulesets |
Persist reference DB Data parameter, allows user to decide when the DB Reference Data should be fetched. If it’s switched on, it will be done during test case creation and stored as a test case payload named Reference DB Data. Otherwise, it will happen during test case execution.
In Test Case Details screen in Payloads section user can refresh this data using button 
or manually edit it by clicking on the Reference DB Data row in edit mode.
...
Option for refreshing Reference DB Data for many test cases at once is available in Int4 API Tester Cockpit main screen. This action can be performed for all test cases in the folder or for the selected items.
...
Variables
...
Variables in Int4 Suite represents a complex feature that allows for data manipulation in the processed test cases. There are various scenarios where Variable processing can be useful:
...
Please see the detailed pages for specific test types for more information.
IDoc Status Validations
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This feature is only available in APITester |
...
IDOC Status Validation parameters are used to override default status handling rules for Inbound and Outbound IDOC test types. Please see the relevant test type (IDoc Inbound, ) manual page for more details.
...