Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
DB Validation Rulesets

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.

https://int4support.atlassian.net/wiki/spaces/IUM/pages/2062843993/Automation+Objects#Database-Validations

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.

...

Used

Parameter name

Description

Example

Description

Free text for the exception rule

Field1

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

Rule to be applied to the field.

  • Warning

Marks the compared fields with yellow color as a "warning".

  • Warning when different based on variable replacement

In case compared values are different Int4 Suite compares them with specified variable. If reference/current value pair from comparison matches variable values result is marked as "warning".

Variable name used for checking the values has to be specified in the Processing Parameter column.

  • Warning when different based on value mapping object

In case compared values are different Int4 Suite compares them with specified values in the Mapping Object. If reference/current value pair from comparison matches mapping values result is marked as "warning".

Mapping Object name used for checking the values has to be specified in the Processing Parameter column.

  • Ignore

Even if it is different in the content, it is not highlighted.

Parameter

  • Change Request

The difference will be highlighted green in the test report.

Note

These rules are active only when Test Case is run within Test Run type: Change Request Test

 

Parameter

Used in correlation with Warning Rules.

...

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

PI: Asynchronous: Direct HTTP operation

If the Direct HTTP URL is provided, here you can specify the HTTP operation (for asynchronous REST testing).

POST

PI: Asynchronous: Direct HTTP URL

Direct endpoint to tested interface (asynchronous). Fulfillment of this parameter is a mandatory condition for testing asynchronous REST/JSON interfaces.

/RESTAdapter/webshop/material_async

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.
Value of this parameter should be aligned with specific format used by tested interface.
Example: If line separator is set to ' and escape character is ? following split is applied:

Source:
NAD+SU+8720121000874::3++Test?'file'NAD+SU+8236459000874

Split:
NAD+SU+8720121000874::3++Test?'file'
NAD+SU+8236459000874

Stop Receiver Processing

Stops Receiver Processing when using PIT as a message injector.

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)

...