...
Parameter name | Description | Example |
Boomi: Operation in Process to get input payload | The name of the operation to get the input payload | listenWebService |
|---|---|---|
Boomi: Operation in Process to get output payload | The name of the operation to get the output payload. | sendIDoc |
Validate message output | This flag allows activating output payload validation for Boomi inbound end-to-end test type. The Boomi validation is performed before the final backend validation, and the results are combined. | X |
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 | CLRFShow XML in the correct order (unsorted) |
Do not fail TC if DB reference not found | This flag determines if the file lines in the XML Comparison Report should be displayed unsorted or should be sorted alphabetically for a specific nodesin 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' - payload will not be sorted on the reportif reference document is not found test case will not be failed Unchecked or '' - payload if reference document is not found test case will be sorted alphabetically failed (default value) |
Test Case Execution
Parameter name
Description
Example
Direct HTTP URL
Direct endpoint to tested interface (synchronous).
It should be provided without Boomi endpoint & port.
Additionally, if the URL is dynamic (like JSON queries), it is possible to enter the variable name in {} brackets. The value will be substituted before calling the final URL
SOAP Action
The SOAP action if the tested interface is a SOAP Webservice
Boomi: HTTP Destination
This is an optional parameter in case there are more than one Atoms per Environment. The RFCs to the specific Atom on which the test case should be executed have to be configured.
The parameter can be environment specific by using the following pattern: LANDSCAPE:DEST
BOOMI_QA_ATOM
environment specific:
DEV:BOOMI_DEV_ATOM
QA:BOOMI_QA_ATOM
Do not fail TC if 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)setting) | ||
Show XML in the original order (unsorted) | This flag determines if the lines of the file in the XML Comparison Report should be displayed in the original order or should be sorted alphabetically for a specific nodes. | Checked or 'X' - payload will not be sorted on the report Unchecked or '' - payload will be sorted alphabetically (default value) |
Test Case Execution
Parameter name | Description | Example |
Direct HTTP URL | Direct endpoint to tested interface (synchronous). Additionally, if the URL is dynamic (like JSON queries), it is possible to enter the variable name in {} brackets. The value will be substituted before calling the final URL | |
|---|---|---|
SOAP Action | The SOAP action if the tested interface is a SOAP Webservice | |
Boomi: HTTP Destination | This is an optional parameter in case there are more than one Atoms per Environment. The RFCs to the specific Atom on which the test case should be executed have to be configured. | BOOMI_QA_ATOM environment specific: |