On completion of the test, you can review the result in the Conditional Connector Test Results dialog:

The Conditional Connector Test Results dialog displays information in the following tabs:

Tabs Description
Results Displays the test results.
Errors Displays any errors that occur while testing a connector's conditional statement.
Logs Displays any log entries generated by the connector after the test has completed.

Results

The Results tab indicates:

  • Whether the expected result ('condition matched' or 'condition not matched') and the actual result of the test are the same. 
  • Whether the input message has passed through the connector.
  • For a Conditional connector, a list of the connector's conditions indicating whether each condition is satisfied by the input message.
Results Panel Description
Test Result

The result of the test:

  • Passed - the test has been executed and the expected result and actual result are the same.
  • Failed - the test was executed and the expected result and actual result are not the same, or fatal errors have occurred while running the test.
  • Executed - the test was executed but not validated as specified by the user. The test has run, with no fatal errors occurring.
 

Whether the input message has passed through the connector:

  • The input message passed through the connector (because all conditions were satisfied).
  • The input message did not pass through the connector (because one or more conditions were not satisfied).
Conditions

Whether the input message satisfied each specified condition (not applicable to a JavaScript connector):

  • The input message satisfied the condition.
  • The input message did not satisfy the condition.

Conditional Connector Testing Errors

The Errors tab displays any fatal errors (exceptions) that occurred when evaluating the connector with the test message.

The errors are typically the same as those that can appear during filter testing, however there are a number of cases specific to conditional connectors:

  • If the route does not have a definition attached to it when testing the Filter messages using a field within the message condition, the following fatal processing error occurs:

    Script exception occurred while testing the message. No appropriate message formats found - failing parse.

  • If the MessageName property is not configured manually when testing the Filter messages using a message type condition, the following fatal processing error occurs: 

    Script exception occurred while testing the message. Exception thrown in script: 
The MessageName property of a message must be set explicitly when testing a 
message type condition.

Conditional Connector Testing Logs

The Logs tab displays any log entries generated while executing the test. The Logs tab is similar in function to that used in filter testing.

When testing a conditional connector (as opposed to a JavaScript connector), the testing framework logs the evaluation of each condition during the test so that a complete trace is available. In addition, any conditions that failed to execute due to an invalid configuration are also logged. This includes, but is not limited to, referenced properties that do not exist, invalid field paths, invalid lookup tables or columns, numeric comparisons where an operand was not a numeric, and invalid regular expressions.

If a JavaScript connector is tested, then any logging is done explicitly via the available log object.