...
Parameter name | Description | Example |
Threshold for searching outbound messages (sec) | If the parameter is not filled, Int4 Suite searches for outbound messages starting from time equal to the beginning of the test run. This parameter extends the range by the values provided in seconds and separated with “,”. E.g., if the test run was started at 07:34:00 and the parameter value is set to “10,15”, it will search for messages from 07:33:50 to 07:34:15. | 10,15 |
Flat File Line Separator | The character used for end-of-line determination in Flat File messages: for example, CLRF - Unix. The parameter is used to display the comparison report better and display the reference and new message line by line. "Carriage Return and New line" character should be stored as CRLF "Line Feed" should be stored as LF (Unix based files) There is no default value, so the parameter is obligatory for CSV files Use || to enter multiple alternative separators e.g. CLRF||' | CLRF |
|---|---|---|
File encoding | Code page of the file. The parameter is used to provide code page information to expression handlers and parses in case code page cannot be determined e.g. from metadata or file header. SAP Code page number is expected as a value. Possible values can are available in the table TCP00. | 1100 (1100 corresponds to ISO 8859-1) |
Show XML in the original order (unsorted) | This flag determines if the lines of the file in the XML Comparison Report should be displayed in the original order or should be sorted alphabetically for a specific nodes. | Checked or 'X' - payload will not be sorted on the report Unchecked or '' - payload will be sorted alphabetically (default value) |
Execute XSLT on input payload (req. TC number with XSLT) | Run XSLT Transformation on input payload before any other execution steps. Test Case number of type XSLT Transformation is expected as an input. | 12345 |
Execute XSLT on input payload after variable replacement | Run XSLT Transformation on input payload after variables are replaced with new values. Test Case number of type XSLT Transformation is expected as an input. | 12345 |
Execute XSLT on ref. output payload(req. TC numb. with XSLT) | Run XSLT Transformation on output reference message (output stored in Test Case as reference). Test Case number of type XSLT Transformation is expected as an input. | 12345 |
Execute XSLT on cur. output payload(req. TC numb. with XSLT) | Run XSLT Transformation on current output message (output generated during Test Case execution). Test Case number of type XSLT Transformation is expected as an input. | 12345 |
Flag for Flat File interfaces | Used to mark interface input as Flat File | X |
Flat Files Compare with payload validations applied | If this checkbox is checked, Payload Validation rules are applied before files comparison and the match content is replaced by the placeholders. This can in some cases result in better flat file comparison results, especially in case of many missing lines. |
...
Parameter name | Description | Example |
Backend system line for current doc. | This parameter points out the system where the tested backend document is stored. The value should be a system line described in the landscape configuration. Note: If Backend system line for the current doc. has the same value as the Backend system line for the reference doc. (for instance, both are S4/HANA) then the RFC connection between the systems will be maintained both in: a) the original environment of the reference document (for instance, production system) b) the environment where the current test case execution takes place (for instance, development system) If Backend system line for the current doc. is different than the Backend system line for the reference doc. then, the RFC connection will be maintained only in the environment of the current execution (for instance, development system), but for both system lines (like ECC and S4HANA) | ECC SAP_ERP |
|---|---|---|
Backend system line for reference doc. | This parameter points out the system line where the reference documents are stored. The value should be a system line described in the landscape configuration. Note: If Backend system line for the current doc. has the same value as the Backend system line for the reference doc. (for instance, both are S4/HANA) then the RFC connection between the systems will be maintained both in: a) the original environment of the reference document (for instance, production system) b) the environment where the current test case execution takes place (for instance, development system) If Backend system line for the current doc. is different than the Backend system line for the reference doc. then, the RFC connection will be maintained only in the environment of the current execution (for instance, development system), but for both system lines (like ECC and S4HANA) | S4HANA |
Payload Matching
...
In scenarios with multiple outputs for the same receiver, there is a need to compare them based on the same order as reference documents used for test case creation.
Integration Platforms don’t guarantee that outputs will always be sent in the same order control; therefore, the solution is to sort the messages before comparison.
Parameter name
Description
Example
Rule
Free text for rule name
Rule1
Expression Type
Expression type. Available options:
unspecified
XPath
Flat expression
This field is optional for all interfaces where there is a single type of output. However, for interfaces that output might be both XML and flat file, it is mandatory to specify the expression type.
XPath
Expression
Path pointing to the field/node where the exception should be applied.
//ORDER/DATE/text() (XPATH expression) or
START_TAG(BGM+220+)&&END_TAG(+)&& (Flat file expression) or
$.order.date (JSONPath expression)
REGEX(BGM\+220\+(.*)\+) (REGEX expression)
Rule Type
Rule type. Available options:
Exact match - value from reference and current payload has to be the same
Variable - value from reference and current payload is compared based on variable values and variable replacement
Mapping object - value from reference and current payload is compared based on mapping object value replacement
Parameter
Depending on Rule type:
variable name
or
mapping object name
Group
Free text grouping field.
All rules with from the same group have to be fulfilled to match payloads.
At least one group has to be fulfilled to match payloads.
Rules within group are linked with AND operator. Groups are linked with OR operator.
Data Scrambling
...
A scramble list is a part of an automation object. For compliance purposes, for example, GDPR purposes, it's required to hide some of the test case fields. Thanks to the anonymizer feature, it's possible to select fields that hold sensitive values and decide what action should be taken to prevent them from being compromised.
...