...
Parameter name | Description | Example |
Database validation ruleset | Reference database validation ruleset object name. Database validation ruleset specify how related backend validation should be performed. Specify tables, fields and join conditions for the backend validation. Buttons allow navigation to the chosen database validation ruleset and creation of a new database validation ruleset | GENERIC_SO |
|---|---|---|
Persist reference DB Data | When switched on, DB reference data will be fetched from backend system during test case creation. Otherwise, it will be fetched during test case execution. |
Dynamic Columns
...
Dynamic Column Set field allows to assign previously defined set to an Automation Object. A dynamic column set defines additional, custom columns in the result list of message selector.
...
Parameter name | Description | Example |
Rule | Free text for rule name | Rule1 |
|---|---|---|
Expression Type | Expression type. Available options:
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) |
Execution Settings
...
Parameter name
...
Description
...
Example
...
Debug Log
...
Int4 Suite will provide additional, more technical information in Test Execution Report during the running of the test cases if this parameter is set. Therefore, it is recommended to set this option initially and deactivate it when object definition is confirmed after executing the first test cases
...
Display wait popup before validation
...
Wait Flag indicating if Int4 Suite should stop test case execution after sending test case message to middleware. Int4 Suite will show the confirmation box, and the user will decide to continue. This setting can execute manual follow-up actions before running the next test case or checking the validations.
This setup works only with Execute via SAP GUI option of execution
...
Rule Type | Rule type. Available options:
|
|
Parameter | Depending on Rule type:
or
|
|
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. |
Execution Settings
Parameter name | Description | Example |
For each test case
Delay (in seconds) between test case execution ( sending message) and checking the results.
10
Once per test run
Delay (in seconds) between test run execution ( sending messages) and checking the results.
60
Number Ranges
...
The number ranges allow generating new values for variables. Those values are used to substitute original document numbers or other values in reference messages.
...
Debug Log | Int4 Suite will provide additional, more technical information in Test Execution Report during the running of the test cases if this parameter is set. Therefore, it is recommended to set this option initially and deactivate it when object definition is confirmed after executing the first test cases | |
|---|---|---|
Display wait popup before validation | Wait Flag indicating if Int4 Suite should stop test case execution after sending test case message to middleware. Int4 Suite will show the confirmation box, and the user will decide to continue. This setting can execute manual follow-up actions before running the next test case or checking the validations. This setup works only with Execute via SAP GUI option of execution |
Delay between execution and validation
Parameter name | Description | Example |
For each test case | Delay (in seconds) between test case execution ( sending message) and checking the results. | 10 |
|---|---|---|
Once per test run | Delay (in seconds) between test run execution ( sending messages) and checking the results. | 60 |
Number Ranges
...
The number ranges allow generating new values for variables. Those values are used to substitute original document numbers or other values in reference messages.
The number range used to replace the source system document number should always be configured to not overwrite the original number. It means that documents generated by Int4 Suite should have their own subset of the original document number. Usually, it might be a subset of the upper limit of the original number range.
...
Parameter name | Description | Example |
Inject using PIT | This flag will use SAP PIT WS as a message injector (SAP PO > 7.5 SP14) for this automation object. This flag can be set up also globally for whole environment. | |
|---|---|---|
HTTP RFC Destination | Alternative RFC Connection where the REST message should be sent. If this parameter is populated, then the message will be sent there alternative RFC. | SAPSYS1_RFC |
Direct HTTP URL | Direct endpoint to tested interface (synchronous). Additionally, if the URL is dynamic (like JSON queries), it is possible to enter the variable name in {} brackets. The value will be substituted before calling the final URL | /RESTAdapter/webshop/salesOrder/ |
Direct HTTP operation | If the direct endpoint is provided, here you can specify the HTTP operation (for synchronous REST testing) | PUT, GET, POST |
PI: Reference Sender Channel Name | Name of the sender channel to be used as a reference. | CC_SOAP_SENDER |
PI: Reference Sender Channel BC | Business Component of the sender channel to be used as a reference. | BC_SENDER |
PI: Reference Sender Channel Party | Party of the sender channel to be used as a reference. | SENDER_PARTY |
Flag for Flat File interfaces | Used to mark interface input as Flat File | |
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 | CLRF |
Line Separator Escape Character | Escape character for line separator. Used to avoid line breaks in case separator is used in the file content. Source: Split: | |
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. | |
Do not fail TC if DB reference not found | This flag determines if in the situation when DB validation for reference messages have not been found whether it should be treated as Error or Successful message. | Checked or 'X' - if reference document is not found test case will not be failed Unchecked or '' - if reference document is not found test case will be failed (default setting) |
...