META-INF.mule-test.xsd Maven / Gradle / Ivy
A component that can be used for testing message flows. It is a configurable component. The return data for the component can be set so that users can simulate a call to a real service. This component can also track invocation history and fire notifications when messages are received.
A component that can be used for testing web services. This component has the same properties as {{component}} element, but in addition to implementing {{org.mule.api.lifecycle.Callable}}, it also implements {{org.mule.api.component.simple.EchoService}}, {{org.mule.tck.testmodels.services.DateService}}, and {{org.mule.tck.testmodels.services.PeopleService}}. When using this with WS endpoints such as CXF, be sure to set the {{serviceClass}} property of the endpoint to the type of service you are using.
Defines the data to return from the service once it has been invoked. The return data can be located in a file, which you specify using the {{file}} attribute (specify a resource on the classpath or on disk), or the return data can be embeddded directly in the XML.
The location of a file to load. The file can point to a resource on the classpath or on disk.
A user-defined callback that is invoked when the test component is invoked. This can be useful for capturing information such as message counts. Use the {{class}} attribute to specify the callback class name, which must be an object that implements {{org.mule.tck.functional.EventCallback}}.
A class name of an object that implements {{org.mule.tck.functional.EventCallback}}.
Whether the component should throw an exception before any processing takes place.
Whether to output all message details to the log. This includes all headers and the full payload. The information will be loogged at INFO level.
Whether the message will be transformed using the transformer(s) set on the inbound endpoint before it gets processed. The default is true.
A fully qualified classname of the exception object to throw. Used in conjunction with {{throwException}}. If this is not specified, a {{FunctionalTestException}} will be thrown by default.
The text of the exception that is thrown. Used in conjunction with {{throwException}}. If this is not specified, an empty message will be used.
Every message that is received by the test component is stored and can be retrieved. If you do not want this information stored, such as if you are running millions of messages through the component, you can disable this feature to avoid a potential out of memory error.
Whether to fire a {{FunctionalTestNotification}} when a message is received by the component. Test cases can register to receive these notifications and make assertions on the current message.
A string value that will be appeneded to every message payload that passes through the component. Note that by setting this property you implicitly select that the message payload will be converted to a string and that a string payload will be returned. The inbound transformer (if any) will get applied first, but if that does not return a string, {{MuleEventContext.getMessageAsString()}} will be called directly after.
The time in milliseconds to wait before returning a result. All processing happens in the component before the wait begins.
The name of this component
A transformer that has no effect.
Deprecated. Transformer has an effect on the message as it can change mime type and encoding. Replace it with a transformer that makes this change explicit.
This component keeps track of the number of times it is executed.
Assertion processor used to assert an expression, invocation count and thread.
Assertion processor used to assert an expression, invocation count and thread of request and response.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy