See: Description
| Interface | Description |
|---|---|
| EventCallback |
The scope of the MuleEvent Callback is to be able to get a the message currently being processed by the
FunctionalTestComponent and make assertions on the message payload, headers or attachments or to make changes required
for the test. |
| FunctionalTestComponent.LifecycleCallback | |
| FunctionalTestNotificationListener |
By implementing this listener interface and registering the object with the
MuleContext.registerListener(ServerNotificationListener) You can receive FunctionalTestNotifications from the
FunctionalTestComponent. |
| Receiveable |
Interface only to be used by the
FunctionalTestComponent. |
| Class | Description |
|---|---|
| AssertionMessageProcessor | |
| CountdownCallback | |
| CounterCallback |
A test callback that counts the number of messages received.
|
| FlowAssert | |
| FunctionalStreamingEchoComponent | |
| FunctionalStreamingTestComponent |
A service that can be used by streaming functional tests.
|
| FunctionalTestComponent |
FunctionalTestComponent is a service that can be used by functional tests. |
| FunctionalTestNotification |
A
FunctionlTestNotification is fired by the FunctionalTestComponent when it receives an event. |
| InvocationCountMessageProcessor |
Test message processor to keep count of number of invocations.
|
| QuietExceptionStrategy |
Restrict exceptions to debug log messages
|
| ResponseAssertionMessageProcessor | |
| SharedConfig |
Test config to test connectors at the domain level
|
| SharedSource |
Test source that is configured with a
SharedConfig. |
| SkeletonSource | |
| StringAppendTestTransformer | |
| TransactionalFunctionalTestComponent |
This service is useful for unit tests involving transactionality because it will roll back the current transaction upon message
arrival.
|
Copyright © 2003–2016 MuleSoft, Inc.. All rights reserved.