Test Recorder in Studio

You cannot create tests for flows with Mule errors raised inside the flow or already existing in the incoming event, even if an on error continue error handler controls them.

A recorded flow execution ends successfully, but the result does not reach its destination because the application is killed.

Your validations fail every time your test runs if you configure spy or assert processors to assert values for random data, time-dependent information (such as timestamps), or values resulting from parallel processes, because those values change in every execution.

Mocking values resulting from parallel processes causes a mixture of real and mocked data that compromises the execution of the processors that follow in your test.

Although the recorder supports data iteration in the flow, such as recursions or loops, it does not support cases in which the structure of the data being tested changes inside the iteration.

The recorder does not support mocking a message before or inside a foreach processor.

When using the Test Recorder to generate a test over your flow, you can only mock parameters included in your flow. You cannot mock parameters in sub-flows or in referenced flows through the Test Recorder UI. If you need to mock parameters in sub-flows of any other process in the project, you can modify the mocking component after creating the test.

Recording a Test from an Exchange Example

Mocking a Message Before and Inside a Foreach Processor