Solace PubSub+ Outbound

Solace PubSub+Outbound is a test that will listen for messages coming to tested queue or topic and will search for the message based on conditions specified in the Variables of Automation Object. It will check the outbound message triggered by other test case or manual action.

Top of the screen with Automation Object (AO) ID, description and test type.

image-20241018-194255.png

 

Basic Information

image-20241018-194436.png

 

 

 

Parameter name

Description

Example

Message VPN

Message VPN id

testservice

Variables

Variables are the container for values that can be used during testing. Each variable contains two values, the one that is calculated based on the reference message/document and the one that is calculated ad-hoc during test case execution.

Variables & Variable processing

Create button allows variable creation.

Parameter name

Description

Example

Name

Variable technical name

VARIABLE_1

Description

Free text for variable description

Variable One

Type

Type of variable processing

Read & Replace

Find message

Custom

Scope

Scope determines the processing of procedures that generate unique values like, e.g., GUID or NUM_RANGE.

  • Test Case Scope - variable is replaced with new values considering values from the currently processed test case. The variable value, which occurs multiple times in the test case payload, is replaced with the same new value. The variable value in different test cases from the currently processed test run is replaced with a new value for each test case.

  • Test Run - variable is replaced with new values considering values from the currently processed test run. The variable value in different test cases from the currently processed test run is replaced with the same new value.

Test Case

Test Run

Payload Validations

Output payloads after processing by Solace PubSub+ are validated against previously stored references. This configuration enables adding rules with exceptions that will allow for differences.

File Type

Processing

XML

XPath

JSON

JSONPath

Flat Files, X12, EDIFACT

Int4 Flat File Syntax or REGEX

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

Used in correlation with Warning Rules.

 

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

 

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

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.

Parameter name

Description

Example

Rule Type

Rule type. Available options:

  • Test Case Creation - in case you want to scramble data during the creation of a test case

  • Runtime - in case you want to scramble data during runtime - when the interface is executed, and additional data is loaded to test case data.

Test Case Creation

Rule

Specify scrambling rule name for identification.

NAME

Method

Choose a scrambling method from a list. Available methods:

  • CONSTANT Replace value with constant
    The current value will contain the constant passed in the parameter. The constant should be provided as is without any brackets.

  • GUID Generate GUID

    Generate random value in a GUID format. 

  • RANDOM Generate a random value

    Generates a random value. The value of the parameter defines the upper limit of the range. It is also possible to generate negative numbers. For example, passing -100 in parameter will generate random numbers from -1 to -100

  • HASH create a hash based on value
    Calculates a hash based on the given value using algorithm passed in parameter (default 'SHA1').

  • MASK - replace each character with constant
    Replace each character with a constant passed in parameter. For example, passing X in the parameter will replace scrambled data with X signs.

  • CUSTOM - create custom method
    create a CUSTOM method (implementing an interface /INT4/IFTT_IF_DATA_SCRMBL_METH).

HASH

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)

Parameter

Specify Processing Parameter suitable for a chosen scrambling method.

X (for Mask method), SHA1 (for HASH Method)

Parameters

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.

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

TestQueue1

Solace PubSub+ Topic pattern

 

Topic name where the message should be published. Value help will show Topics that selected Queue subscribes to.

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

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

Solace PubSub+ REST Delivery Point

 

Rest Delivery Point id created for Int4 Suite

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

rdp_TestSystem

© 2017 - 2022 Int4 AG All rights reserved