This topic contains sections marked as revised for this release
The Events page is the first panel of the Test Client.
The Message Flow Test Events column displays the status and history of the test execution:
Invoke - Starts a new Invoke Message Flow event where the user can fill in a request message and start the test execution.
Saved Messages - Displays the Integration Test Client Data Pool dialog panel in which you can select an XML value structure that was saved in a previous test session.
Stop - Stops the current test.
The detailed properties section displays details of the current message flow being tested:
Message Flow- The name of the message flow being tested.
Input Node – The identifier of the input node being sent in the current message flow. If no MQInput node or HTTPInput node is selected, but are available in the message flow tested, the label no entries is displayed.
The file displays the source of the message flow. You can select which kind of view you would like to use to edit the test message; either the XML structure view or in the XML source view
Use the Testing Client source editor to compose and send test messages when the message flow you wish to send is either in a separate file, or the message is not in XML format and you need to type it in directly
The structured editor allows user-composed XML messages to be viewed in a tree structure table. If the message type is defined in the input node being tested, the structure editor will be pre-populated with an instance of the message type.