--- schema_version: "1" id: 2b4fd45da22b6e29137f8bfa02f47473fb1ede3ffe46bb4c2d36c37131eefd7c title: Testing Projects with MUnit collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/int-test-munit.md canonical_url: https://docs.mulesoft.com/anypoint-code-builder/int-test-munit source_site: docs.mulesoft.com content_type: documentation content_hash: 232835db5fed1b14e1e577f1215e9e640ae5b0291f3c23002584b7b9bd5360ea description: MuleSoft Documentation Site latest: true --- --- product: Anypoint Code Builder version: master --- # Testing Projects with MUnit > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create, run, and modify MUnit tests for your implementation and integration projects in Anypoint Code Builder. Import projects that contain MUnit test files. MUnit is a MuleSoft unit testing framework for creating and running unit tests on a Mule application, as described in [MUnit Overview](https://docs.mulesoft.com/munit/latest/). With MUnit, create MUnit tests and MUnit test suites. An MUnit test is an individual test case, defined by the `` element, which includes specific validations and assertions to test the functionality of a Mule application. An MUnit test suite is a container for multiple MUnit tests. It organizes tests in an XML file typically found in the `/src/test/munit` directory. Anypoint Code Builder provides a **Testing** panel from which you can run tests. In the **Explorer**, test suites are also located within the project directory `/src/test/munit`. Anypoint Code Builder also shows a canvas for creating and maintaining MUnit test suits, a Testing Results panel with the status of tests, and logs that identify the status of tests. Anypoint Code Builder - MUnit Extension, part of the Anypoint Extension Pack, supports MUnit functionality in Anypoint Code Builder. For information about extensions, see [Anypoint Extension Pack](https://docs.mulesoft.com/anypoint-code-builder/#extension-pack). ## Before You Begin Understand the fundamentals of MUnit. Refer to the MUnit documentation for an overview and guidance with test configurations: - [MUnit Overview](https://docs.mulesoft.com/munit/latest/) - [MUnit Test Structure Fundamentals](https://docs.mulesoft.com/munit/latest/munit-test-concept) - [MUnit Event Processors](https://docs.mulesoft.com/munit/latest/event-processors) - [MUnit Cookbook](https://docs.mulesoft.com/munit/latest/munit-cookbook) ## MUnit Tasks and Workflows A workflow can include one or more steps: 1. [Creating tests and test suites](#create-tests) 2. [Opening tests](#open-test) 3. [Running tests](#run) 4. [Debugging](#run-debug) 5. [Fixing errors](#fix-errors) 6. [Importing a project that contains MUnit tests](#import-test) ## Create MUnit Tests and Test Suites Configure MUnit tests and test suites directly from a flow or by using the canvas or code editor. - [Create an MUnit Test Suite](#create-suite) - [Create an MUnit Test](#create-test) ### Create an MUnit Test Suite Create an MUnit test suite in your project from the **Explorer**. 1. Open your project to `/src/test/munit` in the **Explorer**. 2. Create a suite file in the `munit` folder: 1. Right-click the `munit` folder and select **New MUnit Test Suite File**. 2. Provide a name for your suite, such as `my-suite.xml`. A canvas shows with a link to build a new test with scope and flow structure options. The new suite file includes the XML declaration (``), `` and `` elements. For example: ```xml ``` 3. Select a component from the canvas to customize your test: - With the **Behavior** components, such as 'munit:before-test', 'munit:after-test', etc., you can set the conditions for the test. - With the **Execution** components, the '' or inline flow definition within the '' block, you can specify the actions or processes to test. - With the **Validation** components, such as 'munit:assert-that', you can check the output or state of the application after the execution phase to ensure it matches the expected results so you can confirm the application behaves as intended. See [MUnit Event Processors](https://docs.mulesoft.com/munit/latest/event-processors) for more information. 4. Continue to [Create an MUnit Test](#create-test). > [!NOTE] Anypoint Code Builder requires MUnit 3.4.0 or later to create MUnit test suites from the > canvas. ### Create an MUnit Test Create an MUnit test in a new or existing test suite. Start an MUnit test by right-clicking the `flow` component, or by using the canvas or code editor. For guidance with your test configuration, refer to the [MUnit documentation](#prereqs) described in the prerequisites. #### Create a Test from a Flow Generate the basic structure for an MUnit test designed to test a specific flow within your Mule application. 1. Open your Mule project. 2. In the canvas, right-click on the `flow` component. 3. Select **Create Test**. 4. Anypoint Code Builder creates a new MUnit test suite file in your project `/src/test/munit` folder with the test structure targeting the selected flow. #### Create a Test from the Canvas 1. Open an MUnit test suite file in the `src/test/munit/` folder. 2. Click **Add**, and then select **Test scope**. 3. In the panel that appears, select **Test**. 4. Anypoint Code Builder creates an empty test in the currently open test suite. #### Create a Test from the Code Editor 1. Open the test suite XML in the code editor. For guidance, see [Open MUnit Tests](#open-test). 2. In the code editor, press Ctrl+Space to display available options, and type `munit`. For example: ![Using autocomplete in the code editor to select the MUnit test element](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-tests-test-xml-autocomplete.png) 3. Select `munit:test` and insert the test element in your suite. For example: ```xml ``` 4. Provide a name and other XML elements to create the test. For example, on any line within XML similar to these examples: ```xml ``` To find more examples, see [MUnit Examples](#examples). 5. Run your test from the Test panel. For guidance, see [Run MUnit Tests](#run). ## Open MUnit Tests Open the test suite XML from the **Testing** panel or the **Explorer**. After the February 2025 release, Anypoint Code Builder shows a canvas with the test components, or provides a link to build a new test. > [!NOTE] Anypoint Code Builder requires MUnit 3.4.0 or later to create MUnit test suites from the > canvas. - **Testing panel** - Open the **Testing** panel from the activity bar: 1. Open a project that contains an MUnit test suite. 2. Click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-testing.png) (**Testing**) to open the **Testing** panel. 3. Click or hover the suite or test name, and click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-go-to-test-gray.png) (**Go to test**) or highlighted ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-go-to-test.png) (**Go to test**) to open the XML file that contains the test. Clicking the test name also opens to the XML file. - **Explorer** - From the **Explorer**, locate MUnit test suite files in the project directory: 1. Open a project that contains an MUnit test suite. 2. In the activity bar, click (![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-explorer.png)) (**Explorer**). 3. Go to `src/main/test/munit`. 4. Click a test suite XML file to view the tests in the suite. ## Run MUnit Tests Run MUnit tests using any of these options: - [Run Tests from the Testing Panel](#run-test-panel) - [Run Tests from the Canvas](#run-test-canvas) - [Run Tests from the MUnit Configuration XML File](#run-test-xml) - [Run Tests with an MUnit Launch Configuration](#run-launch-config) - [Run MUnit Tests in Debug Mode](#run-debug) - [Run MUnit Tests with Coverage](#run-coverage) If you run a test, a test build executes, and the Terminal displays the progress of the test. If all tests execute successfully, the build succeeds. Otherwise, the build fails. Anypoint Code Builder displays the results of the tests in the **Testing** panel, the **Terminal**, and the **Test Results** panels. Time-stamped logs are also available from the **Test Results** panel. You can clear the results at any time. ### Run Tests from the Testing Panel Run all tests, all tests in a suite, or a single test from the **Testing** panel. The **Testing** panel lists all MUnit test suites in the project. To run tests: 1. Open a project that contains an MUnit test suite. To check for test suites, see [Open MUnit Tests](#open-test). 2. From the activity bar, click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-testing.png) (**Testing**) to open the **Testing** panel. If the icon isn’t present, try right-clicking within the activity bar and selecting **Testing** to display the icon. 3. Run tests from the **Testing** panel at any of three levels: ![Testing panel](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-testing-panel.png) Run tests with or without debugging features. If your XML contains breakpoints and you opt to debug, test execution stops at your breakpoints. For information about debugging, see [Run MUnit Tests in Debug Mode](#run-debug).
1All suites: to run all tests in all suites, click the Run Tests, Debug Tests, or Run Tests with Coverage icon. You can select the same options from the right-click menu.
2Suite: to run all tests in a single suite, hover over, or click the suite, and then click the Run Test, Debug Test, or Run Test with Coverage icon. You can select the same options from the right-click menu.
3Test: to run a single test, hover over, or click a test in a test suite, and then click the Run Test, Debug Test, or Run Test with Coverage icon.
You can select the same options from the right-click menu. 4. Monitor the test and review test results: - **Testing** panel and XML: The following example displays a running test. ![Running test in the Test panel and XML](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-xml-test-run-panel-xml.png) After the test runs, the panel and XML show the result. - Terminal: The following example provides the progress of a test that runs and fails. \================================================================================ === Running suite: myTestSuiteEx3.xml === ================================================================================ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ - Running test: test-03-suite3 + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ java.lang.AssertionError: at file: \[myTestSuiteEx3.xml\], line: \[27\] Expected: "this" as String {encoding: "UTF-8", mediaType: "application/java; charset=UTF-8", mimeType: "application/java", class: "java.lang.String", contentLength: 4} but: "that" as String {encoding: "UTF-8", mediaType: "application/java; charset=UTF-8", mimeType: "application/java", class: "java.lang.String", contentLength: 4} at (root) at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ \[INFO\] =============================================================================== \[INFO\] MUnit Run Summary - Product: MULE\_EE, Version: 4.6.0 \[INFO\] =============================================================================== \[INFO\] >> myTestSuiteEx3.xml test result: Tests: 1, Errors: 0, Failures: 1, Skipped: 0 \[INFO\] --- test-03-suite3 <<< FAILED \[INFO\] \[INFO\] =============================================================================== \[INFO\] > Tests: 1 \[INFO\] > Errors: 0 \[INFO\] > Failures: 1 \[INFO\] > Skipped: 0 \[INFO\] =============================================================================== \[INFO\] ------------------------------------------------------------------------ \[INFO\] BUILD FAILURE \[INFO\] ------------------------------------------------------------------------ \[INFO\] Total time: 03:10 min \[INFO\] Finished at: 2024-04-29T08:49:39-07:00 \[INFO\] ------------------------------------------------------------------------ 5. If the test results indicate any failures, go to [Fix Test Errors](#fix-errors). To clear test results, see [Clear Test Results](#clear-results). ### Run Tests from the Canvas Run a test, with or without coverage. Add a test scope to test specific parts of your Mule application or flow structure to define the execution context. ![Running a test from the canvas](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-run-test-canvas.png) See [Create MUnit Tests and Test Suites](#create-tests). See [Run MUnit Tests with Coverage](#run-coverage). ### Run Tests from the MUnit Configuration XML File Run tests with or without debugging features. If your XML contains breakpoints and you opt to debug, test execution stops at your breakpoints. For information about debugging, see [Run MUnit Tests in Debug Mode](#run-debug). To run tests from the test suite XML: 1. From the **Testing** panel, open a test suite XML file in your project. For guidance with opening from the **Testing** panel, see [Open MUnit Tests](#open-test). 2. Run a single test or all tests in the test suite XML file: ![Testing options from test suite XML](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-xml-test-options.png) - To run a single test in the test suite XML: 1. Place your cursor on a line that contains the XML for a test (`munit:test`). For example, on any line within XML similar to this example: ```xml ``` 2. Right-click, and select an option: - **Run Test at Cursor** - **Debug Test at Cursor** - **Run Test at Cursor with Coverage** If you don’t see these menu items, be sure to open the XML file from ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-go-to-test-gray.png) or highlighted ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-go-to-test.png) (\*Go to test\*) in the \*Testing\* panel. - To run all tests in the test suite XML: 1. Place your cursor in the XML file. 2. Right-click, and select an option: - **Run Tests in Current File** - **Debug Tests in Current File** - **Run Tests with Coverage in Current File** If you don’t see these menu items, be sure to open the XML file from ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-go-to-test-gray.png) or highlighted ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-go-to-test.png) (\*Go to test\*) in the \*Testing\* panel. 3. Check the status of the running test in the Testing, Terminal, and Testing Results panels. See the [example](#results-example). To clear test results, see [Clear Test Results](#clear-results). ### Run Tests with an MUnit Launch Configuration Run MUnit tests from the Run and Debug panel with an MUnit launch configuration. Create and run an MUnit launch configuration: 1. Open the Run and Debug panel. Show me how - Click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-run-debug.png) (**Run and Debug**) icon in the activity bar. - Use the keyboard shortcuts: - Mac: Cmd+Shift+d - Windows: Ctrl+Shift+d - Select **View** > **Run**. 2. Add a launch configuration to `launch.json`: 1. Click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-gear.png) (gear icon) to open the **launch.json** tab. The default configuration looks something like this: ```json { "version": "0.2.0", "configurations": [ { "type": "mule-xml-debugger", "request": "launch", "name": "Debug Mule Application", "mule.project": "${workspaceFolder}", "mule.runtime.args": "${config:mule.runtime.defaultArguments}" } ] } ``` 2. In the `launch.json` file, add a comma after the first object in the array, and append the MUnit launch configuration by pressing Ctrl+Space to open the auto-complete menu and selecting **MUnit Debug Launch**. For example: ![Adding launch configuration for MUnit from the auto-complete menu](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-launch-config-autocomplete.png) This action adds a new JSON object named `Munit Debug Tests` to the file. For example: ```JSON { "version": "0.2.0", "configurations": [ { "type": "mule-xml-debugger", (1) "request": "launch", "name": "Debug Mule Application", "mule.project": "${workspaceFolder}", "mule.runtime.args": "${config:mule.runtime.defaultArguments}" }, { "type": "munit-xml-debugger", (2) "request": "launch", "name": "Munit Run Tests", "mule.project": "${workspaceFolder}", "munit.runtime.args": "${config:munit.runtime.defaultArguments}", "munit.runtime.debugger.version": "${config:munit.runtime.debugger.version}", "munit.debug": "false" } ] } ```
1Launcher for the standard debugger, named Debug Mule Application.
2Launcher for the MUnit debugger, named Munit Run Tests.
3. Save the configuration to `launch.json`. 4. Run MUnit tests from the **MUnit Debug Tests** launch configuration: 1. In the Run and Debug panel, select **MUnit Debug Tests** from the launch menu. For example: ![Selecting MUnit Debug Tests from the launch menu](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-launch-config-munit.png) 2. Execute **MUnit Debug Tests** by clicking ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-start-debug.png) (launch) in the **Run an Debug** panel. 5. Verify that the MUnit tests run. See the [example](#results-example). ## Run MUnit Tests in Debug Mode Run your test in debug mode after adding breakpoints to the XML for your tests or Mule application. When Mule reaches the breakpoint, you can review variables in the Run and Debug panel. 1. Open a project that contains an MUnit test suite. 2. Add breakpoints to the XML for the Mule application or test suites. For guidance with breakpoints, the Mule event, DataWeave in the **Watch** panel and **Debug Console**, conditional breakpoints, and exception breakpoints, see [Debugging Mule Applications](https://docs.mulesoft.com/anypoint-code-builder/int-debug-mule-apps). 3. Run your test with a debugging command using one of the following options: - From the **Testing** panel, click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-run-debug.png) (**Debug test**) at any level (all tests, all tests in a suite, or a single test). For more guidance, see [Run Tests from the Testing Panel](#run-test-panel). - From the suite XML, use the right-click menu to run the test. For more guidance, see [Run Tests from the MUnit Configuration XML File](#run-test-xml). - From a launch configuration in the Run and Debug panel. For guidance, see [Run Tests with an MUnit Launch Configuration](#run-launch-config). 4. When the build process reaches a breakpoint, click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-run-debug.png) (**Run and Debug**) from the activity bar to review variables, including the Mule event variables and test parameters. For example: ![Variables after debugging test with breakpoints](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-debug-test-mule-event.png) 5. Examine the data, and address any issues. By default, running tests fail after a timeout period. If a debugging session reaches a breakpoint in a test, the test and the build fail at timeout. See [Test TimeOut Attribute](https://docs.mulesoft.com/munit/latest/munit-test-concept#test-timeout-attribute). ## Run MUnit Tests with Coverage Run your test with coverage to measure how much of a Mule application your set of MUnit tests executes. 1. Open a project that contains an MUnit test suite. 2. Run your test with coverage using one of the following options: - From the canvas, click **Run Test** and **Run Test with Coverage**. The **Testing** panel shows the test coverage results. For more guidance, see [Run Tests from the Canvas](#run-test-canvas). - From the **Testing** panel, click **Run Test with Coverage** at any level (all tests, all tests in a suite, or a single test). For more guidance, see [Run Tests from the Testing Panel](#run-test-panel). - From the suite XML, right-click and select an option to run the test. For more guidance, see [Run Tests from the MUnit Configuration XML File](#run-test-xml). 3. After the test suite runs, view coverage results using one of the following options: - In the activity bar, click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-testing.png) (**Testing**) to open the **Testing** panel. The **Test Coverage** panel shows coverage for directories and files: ![Test coverage percentages after running tests with coverage](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-test-coverage-panel.png) - In the activity bar, click (![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-explorer.png)) (**Explorer**), which shows coverage for directories and files. Numeric and graphic percentages both show the percentage of event processors executed by the MUnit test. ## Fix Test Errors After [running a test](#run), fix any errors. 1. Review test errors in the XML by clicking the name of the failing test from the **Testing** panel. The error in the XML example identifies the error `java.lang.AssertionError`. - Expected result (highlighted in red): "yes" as String {encoding: "UTF-8", mediaType: "application/java; charset=UTF-8", mimeType: "application/java", class: "java.lang.String", contentLength: 3} - Actual result (highlighted in green): "no" as String {encoding: "UTF-8", mediaType: "application/java; charset=UTF-8", mimeType: "application/java", class: "java.lang.String", contentLength: 2} at (root) You can also review the test results in the **Test Results** panel by clicking the failing test in the test logs. For example: ![Error in the Test Results panel](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-test-results-panel-failed.png) 2. Fix the error: 1. After reviewing the error, click the **x** icon to close the error message in the XML. For example: ![Closing test error messages in the XML](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-test-error-xml-close.png) 2. Edit the XML to produce the expected output. For example, the failing test case in the example must return `"yes"` instead of `"no"`. 3. After fixing the error, rerun the test to ensure that the fix works: - To rerun the test from the XML, click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-failed-test.png) (**Test failure**) for the test. - To rerun the test from the **Testing** panel, click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-run-test.png) (**Run test**). - To rerun the test from the Testing Results panel, open the panel, click the name of the failing test in the test logs, and click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-run-test.png) (**Run test**) from the test logs. For guidance with MUnit XML configurations, see [MUnit Test Structure Fundamentals](https://docs.mulesoft.com/munit/latest/munit-test-concept) and [MUnit Event Processors](https://docs.mulesoft.com/munit/latest/event-processors). ### Troubleshoot Runtime Class Errors If running a test fails with an error similar to `NoClassDefFoundError: org/apache/commons/io/output/ByteArrayOutputStream`, check your project and runtime setup before changing test logic. 1. Verify compatibility among Mule runtime, MUnit dependencies, and the Anypoint Code Builder extensions that you are using. 1. Confirm the versions that your project declares in `pom.xml`. 2. If needed, align dependency and plugin versions with the versions recommended in [MUnit Overview](https://docs.mulesoft.com/munit/latest/). 2. Clean and rebuild the project, and then rerun the test. 1. From the terminal, run `mvn clean test` to confirm whether the issue reproduces outside the IDE test runner. 3. Review dependency declarations in `pom.xml` for conflicts in test dependencies, including direct overrides for `commons-io`. 4. If the error persists, isolate the issue in a new minimal project and compare the project dependencies and plugin versions. 5. Capture the full terminal stack trace and contact support if the runtime class error continues after version and dependency checks. To clear test results, see [Clear Test Results](#clear-results). ## Import a Project that Contains MUnit Tests Mule projects created in Anypoint Studio and Anypoint Code Builder for your integrations or implementations can include MUnit tests. - To import and open the project into Anypoint Code Builder, see [Importing Projects into Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/int-import-mule-project). - To export a project from Anypoint Studio before importing to Anypoint Code Builder, use one of the procedures in [Export Projects From Studio](https://docs.mulesoft.com/studio/import-export-packages#export-project-studio). - To start an integration that imports an example or template that contains MUnit tests from Anypoint Exchange, see [Create an Integration Project](https://docs.mulesoft.com/anypoint-code-builder/int-create-integrations#create-integration-project). Instead of starting with an empty project when creating the integration project, click **Template or Example Project** so that you can import the asset that contains tests into your project. ## Clear Test Results After testing, you can clear test results from the **Testing** panel and the logs if you no longer need them. - From the **Testing** panel, click the **Views and More Actions** (**…​**) menu, and select **Clear All Results**. - From the **Test Results** panel, click ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-munit-clear-test-results.png) (**Clear All Results**). For example: ![Clearing test results from Test Results panel](/mulesoft/current/en-us/anypoint-code-builder/_images/munit-clear-testing-results-log.png) ## Targeting Specific Processors and Attributes in Your Test Add these processors to your MUnit test to focus on individual components of your Mule flow:
ProcessorDescription

Mock-when

Create a mock of an event processor in your flow to simulate the behavior of the event processor without executing it.

Spy

Observe what happens before and after a specific event processor in your flow is executed, without altering its behavior.

### Setting Up Processors 1. On your test suite, click **+**. 2. Search for a processor designed to observe your flow (see [Targeting Specific Processors and Attributes in Your Test](#targeting-specific-processors-and-attributes-in-your-test)). 3. Select the type of processor to be observed by clicking on the **+** icon. ![Component window to add a processor](/mulesoft/current/en-us/anypoint-code-builder/_images/acb-munit-processor.png) 4. Select the components and attributes of the processor to observe. ![Component and attribute highlighted in the processor window](/mulesoft/current/en-us/anypoint-code-builder/_images/acb-munit-select-component-attribute.png) 5. Click **Add** to add the processor to your test suite. The processor shows in the code editor and the canvas. When selecting the processor and its attributes, consider these aspects: - The configuration for one processor applies to all processors of the same type in your flow. - The attributes of all processors of the same type are listed. ## MUnit Examples The MUnit documentation provides several examples. See [MUnit Cookbook](https://docs.mulesoft.com/munit/latest/munit-cookbook). The following MUnit test example validates if the `payload` is the string `"Example"`: ```xml ``` For information about `munit:execution`, `munit:validation`, and other MUnit testing elements, see [MUnit Test Structure Fundamentals](https://docs.mulesoft.com/munit/latest/munit-test-concept) and [MUnit Event Processors](https://docs.mulesoft.com/munit/latest/event-processors).