The runJUnitTests operation allows for running JUnit tests on Mule Servers. Although this operation was not designed for use with Mavenized Mule projects, it will run tests on them as well, and could serve to prove that the <provided> scope jars are indeed provided by the Mule server.startApplication operation starts a stopped Mule Application. It can be used in build or deploy workflows.
This operation is compatible with the following types of servers:
| Server Type | Notes |
|---|---|
| CloudHub | |
| Anypoint Runtime Manager | |
| Runtime Agent | |
| Standalone | This operation should run on the Mule server where the project will be |
...
The project tests will be built using javac and other command line tools.
This operation should be run after the buildMule operation, and on the same endpoint, environment, and instance.
...
| started. |
Environment/Instance Properties
...
Property Name | Property Code | Required for which server Types | Description |
|---|---|---|---|
FDMULE_APP_NAME | All | ||
FDMULE_HOMEYes | Standalone | ||
| FDMULE_USER | |||
| FDMULE_PASSWORD | |||
| FDMULE_TYPE | All | ||
| FDMULE_ORG_NAME | |||
| FDMULE_ENV_NAME | |||
| FDMULE_TIMEOUT | |||
| FDMULE_TARGET_TYPE | |||
| FDMULE_TARGET_NAME | |||
| FDMULE_STATIC_IPADDRESS |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Mule Project Path | FDMULE_PROJECT_PATH | No | This is the folder that typically is named for your application and contains your [src] folder. Relative paths are sourced from the FD_TEMP_DIR. |
| http.port | FDMULE_HTTP_PORT | No | HTTP port to use when running JUnit tests. This should be a different number than the one that is usually used to run the application on the server. This only works if |
...