Azure Service Bus is a test that will inject the message to the Microsoft Azure Service Bus queue. It will perform validation of the middleware platform outbound message as well as validate database entries created by the message processing in the backend ABAP based system.
Payload for this test type has to be manually provided in the APITester Cockpit.
Basic Information
...
Parameter name | Description | Example |
Queue name | Microsoft Azure Service Bus queue name | queue1 |
|---|
...
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.Link to be added
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 Test Run |
Payload Validations
...
Output payloads after processing by SAP PI/PO are validated against previously stored references. This configuration enables adding rules with exceptions that will allow for differences.
File Type
Processing
XML
JSON
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 |
|
...
Parameter name | Description | Example |
HTTP RFC Destination | Type G RFC destination pointing to server where Service Bus queue is deployed | AZURE_SB1_HTTP_DEST |
|---|
...
Add labelAdd label
XSLT Transformations
XSLT Transformation can be applied on both Input and Output payloads and it is stored in a reference test case of type XSLT Transformation. To call XSLT Transformation during Test Case execution, Test Case number that is of type XSLT Transformation needs to be provided as an input to one of the below parameters.
Parameter name | Description |
Execute XSLT on input payload | Run XSLT Transformation on input payload before any other execution steps |
|---|---|
Execute XSLT on input payload after variable replacement | Run XSLT Transformation on input payload after variables are replaced with new values |
Execute XSLT on ref. output payload | Run XSLT Transformation on output reference message (output stored in Test Case as reference) |
Execute XSLT on cur. output payload | Run XSLT Transformation on current output message (output generated during Test Case execution) |
Example usage of XSLT transformations can be found here https://int4support.atlassian.net/wiki/spaces/IUM/pages/1230602260/XSLT+transformation+examples#Different-order-of-XML-nodes-in-a-new-solution.