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.
...
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 |
HTTP RFC Destination | Type G RFC destination pointing to server where Service Bus queue is deployed | AZURE_SB1_HTTP_DEST |
|---|
Add 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.