This topic contains sections marked as revised for this release
You can test sending messages when you are developing message flows before you deploy them using the Test Client.
The testing starts when a message-flow event is invoked and ceases with a Stop event.
One execution can be performed at the same time in the Test Client.
A test can be stopped manually or automatically depending on the situation. Stopping the test has no effect on the runttime, and will only disconnect the monitors that are running.
A synchronous test, as would be the case when the message flow invoked from an HTTPInput node, is stopped automatically when a reply message is received.An asynchronous test, as would be the case when the message flow is invoked from an MQInput node, can be stopped manually depending on the monitor setting in the configuration panel.
All execution events are stopped when the Test Client is closed and any test monitors are removed.