Versions Compared

Version Old Version 1 New Version Current
Changes made by

Bartosz Komendacki

Bartosz Komendacki

Saved on

Key

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

...

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.

  • 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

Solace PubSub+ Fetch From

Fetching from Queue or Topic.

When Fetching from Queue, program will do the following:

  1. Create Queue Binding - connect tested queue with Int4 Suite REST Delivery Point specified in other parameter (and created during technical preparation phase)

  2. Wait for messages to arrive in buffer table

  3. Match the messages based on variables configuration

  4. Delete Queue Binding

When Fetching from Topic, program will do the following:

  1. Subscribe tested topic to Int4 Suite technical queue (created during technical preparation phase)

  2. Wait for messages to arrive in buffer table

  3. Match the messages based on variables configuration

  4. Delete topic subscription for Int4 Suite technical queue

Queue, Topic

Solace PubSub+ Queue

Solace PubSub+ Queue ID, where the message should be published. Value help will show Queues available in the Selected Message VPN.

Info

Applicable only if Queue was selected in Solace PubSub+ Post to parameter.

TestQueue1

Solace PubSub+ Topic pattern

 

Topic name or topic pattern where the message should be published. Value help will show Topics that selected Queue subscribes to. More about topic patterns can be found at Solace PubSub+ Topic Patterns

Info

Applicable only if Topic was selected in Solace PubSub+ Post to parameter.

int4suite/demo12/s4/beh/us/salesorder/Created/v1

int4suite/demo15/s4/beh/us/salesorder/>

int4suite/demo*/s4/beh*/us/salesorder/Created/v1

Solace PubSub+ REST Delivery Point

Rest Delivery Point id created for Int4 Suite

Info

Applicable only if Queue was selected in Solace PubSub+ Fetch From parameter.

rdp_TestSystem