``` You can also configure this from the `pom.xml` configuration: ```xml com.mulesoft.munit.tools munit-maven-plugin ... exampleMunitTag ... ``` You can specify more than one tag by separating them with a comma. ### Fail When No Tests Run By default, MUnit fails the Maven build if it can’t find any MUnit test suites or if no tests run from the discovered suites. This behavior helps ensure that applications in a CI pipeline include and run MUnit tests. To allow a build to succeed when no MUnit tests run, set `munitFailIfNoTests` to `false` in the MUnit Maven Plugin configuration: Allow builds with no MUnit tests ```xml com.mulesoft.munit.tools munit-maven-plugin ... false ... ``` You can also disable this behavior from the command line: ```console mvn clean test -Dmunit.failIfNoTests=false ``` Use this setting only when no MUnit tests are expected to run. Maven’s `skipTests` parameter and MUnit’s `skipMunitTests` parameter skip MUnit test execution and don’t run this validation. ### Skip All Tests MUnit leverages the same mechanism as Maven. To skip tests, you must use the `skipTests` parameter: Skip Tests example ```console mvn clean package -DskipTests ``` You can also configure this from the `pom.xml` configuration: ```xml com.mulesoft.munit.tools munit-maven-plugin ... true ... ``` ### Skip Tests After One Suite Fails MUnit allows you to skip the rest of the tests if one test suite fails: ```xml com.mulesoft.munit.tools munit-maven-plugin ... true ... ``` If not specified, it’s default value is `false`. ## Specify the Runtime Product You can specify the type of runtime in which the applications you test run. Accepted values are: - `MULE` for the Mule Kernel (formerly called Mule Community Edition) - `MULE_EE` for the Mule Enterprise Edition ```xml com.mulesoft.munit.tools munit-maven-plugin ... MULE ... ``` ### Specify the Runtime Product Version You can specify the runtime version in which the applications you test run. ```xml com.mulesoft.munit.tools munit-maven-plugin ... 4.2.2 ... ``` The `munit.runtimeversion` property replaces the deprecated `runtimeVersion` property. The `runtimeVersion` property remains supported. If you use `runtimeVersion`, MUnit displays a warning message that indicates the property is deprecated and that you must migrate to `munit.runtimeversion`. ## Specify the JVM You can specify the JVM (or the Java executable) in which the applications you test run. You must populate the `munit.jvm` parameter with the path to the executable: Specify the JVM ```console mvn clean package -Dmunit.jvm=/path/to/jdk/bin/java ``` You can also configure this from the `pom.xml` configuration: ```xml com.mulesoft.munit.tools munit-maven-plugin ... /path/to/jdk/bin/java ... ``` ### Additional Argument Lines You can pass additional argument lines to the JVM. Specify each argument in a separate `argLine`: Argument lines ```xml com.mulesoft.munit.tools munit-maven-plugin ... -XX:MaxPermSize=512m -Xmx1024m ... ``` ### Environment Variables To set additional environment variables during the test run, you can specify them with the respective key and value: Additional Environment Variables ```xml com.mulesoft.munit.tools munit-maven-plugin ... exampleValue val2 ... ``` As shown in the previous example, you can use environment variables to replace placeholders such as `${MY_ENV}`. ### System Properties Variables If you must define specific system variables to run your MUnit test successfully: Setting system property variables ```xml com.mulesoft.munit.tools munit-maven-plugin ... my.property.value ... ``` Depending on the execution context, the system property values can vary. When referencing these properties, you must override their value to enforce test reproducibility. You can do so by using the `-D` argument when running MUnit with Maven. Variables passed with the `-D` argument take full priority over any other property. For example: ```none -Dmy.property.key=my.property.another.value ``` ## Redirect Test Output to File When running several tests, the build output can get very complex to read. MUnit allows you to redirect the output of each test suite to a file. This way, the test results remain in the build output and you can check the respective file to check the standard output of each test suite. You can find these files in the `testOutputDirectory` folder following the naming convention: `munit.${suiteName}-output.txt`, where `suiteName` represents the name of the XML file relative to the MUnit test folder. The test output that doesn’t belong to a particular suite isn’t printed to keep the build output clean. You can enable it by running Maven in debug mode. To redirect the output of each test suite to a file: Redirect test output to a file ```xml com.mulesoft.munit.tools munit-maven-plugin ... true ... ``` By default, it’s set to `false`. ### Test Output Directory If you want to choose the location where the test creates the output files, the path specified can be absolute or written as a Maven placeholder: Test output directory with absolute path ```xml com.mulesoft.munit.tools munit-maven-plugin ... /my/absolute/path ... ``` Test output directory using Maven placeholders ```xml ${project.build.directory}/my/output/folder ``` By default, the files are created in `${project.build.directory}/munit-reports/output/`. ## MUnit Maven Plugin Configuration Reference The MUnit Maven Plugin offers a set of optional configurable parameters.

Table 1. Maven Plugin Parameters
Name	Type	Description
`argLines`	List	Additional JVM argument lines to set on the test run.
`coverage`	Configuration	Coverage configuration to set on the test run.
`dynamicPorts`	List	Dynamic ports to set on the test run.
`enableSurefireReports`	boolean	Set value to `true` to generate MUnit test results in the Surefire format. Its default value is `true`.
`munitTest`	String	Name of the MUnit tests to run.
`munitTags`	String	Name of the MUnit tags. Tests tagged with these names run.
`munitFailIfNoTests`	boolean	Fails the Maven build if no MUnit test suites are found or no tests run from the discovered suites. Its default value is `true`.
`skipMunitTests`	boolean	Setting this parameter to `true` skips all MUnit tests. Its default value is `false`.
`skipAfterFailure`	boolean	Skip all tests if one fails. Its default value is `false`.
`munitTestsDirectory`	File	Directory where the MUnit tests reside. Its default value is `${project.build.directory}/test-mule/munit`.
`munit.runtimeversion`	String	Version of the Mule runtime When you run your tests from Maven, this value comes from the `minMuleVersion` parameter in the `mule-artifact.json` file. To modify the Mule runtime version used to run your MUnit tests, see Runtime Patching.
`runtimeVersion` (deprecated)	String	Deprecated alias for `munit.runtimeversion`. This property remains supported for backward compatibility. When you use this property, MUnit displays a warning message and instructs you to migrate to `munit.runtimeversion`.
runtimeProduct	String	Type of runtime. Expected values are: `MULE` for the Mule Kernel (formerly called Mule Community Edition) `MULE_EE` for the Mule Enterprise Edition By default, this value comes from the `requiredProduct` parameter in the `mule-artifact.json` file.
`jvm`	String	Option to specify the JVM (or path to the Java executable) to use. By default, the JVM is the same VM as the one used to run Maven.
`environmentVariables`	Map	Additional environment variables to set on the test run.
`redirectTestOutputToFile`	boolean	Setting this value to `true` redirects the MUnit tests standard output to a file. Its default value is `false`.
`systemPropertyVariables`	Map	System properties set on the test run.
`testOutputDirectory`	File	Directory where the test outputs are written. Its default value is `${project.build.directory}/munit-reports/output/`.