FunctionalTestProcessor.getAppendString() to the contents of the message.FlowAssert#verify(String))
afterwards.FlowAssert#verify(String)) afterwards.FunctionalTestProcessor and make assertions on the message payload, headers or attachments or to make changes required
for the test.FunctionlTestNotification is fired by the FunctionalTestProcessor when it receives an event.NotificationListenerRegistry.registerListener(NotificationListener) You can receive
FunctionalTestNotifications from the FunctionalTestProcessor.FunctionalTestProcessor is a service that can be used by functional tests.cursors to not be closed when the executed flow is finished but when the test is disposedInternalEvent from a test connector's queue.InternalEvent to a test connector's queue.ObjectFactory for test:component return-data element.FlowAssert#verify(String))
afterwards.FlowAssert#verify(String)) for each
flowNamesToVerify afterwards.SharedConfig.Message and InternalEvent.Message and InternalEvent.ComponentBuildingDefinitions to parse TEST module configuration.Processor implementation that will return control to the Flow in a custom Scheduler
thread in the same way as, for example, a HTTP requester would.XmlNamespaceInfoProvider for TEST module.FunctionalTestException.TransactionConfig.InternalEvent to the configured flow.Message.getAttributes() value of the produced messagecorrelation.correlation.Message.getAttributes() instead.Message.getAttributes() instead.Message.getAttributes() instead.Message.getAttributes() instead.InternalEvent to the configured flow.InternalEvent to the configured flow.Message.getAttributes() instead.Message.getAttributes() instead.InternalEvent to the configured flow.Flow as a task of a given Scheduler.sourceCorrelationId.sourceCorrelationId.Message to the configured flow.Message to the configured flow.Copyright © 2003–2017 MuleSoft, Inc.. All rights reserved.