Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.

This operation should run on the Mule server where the project will be deployed. The FDMULE_HOME property is used to find the libraries that are necessary to compile and run the Mule project tests.

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.

Make sure that the JDK HOME specified on the endpoint is a JDK of the required version.


Environment/Instance Properties

Property Name

Property Code

Required

Description





Project Properties

Property Name

Property Code

Required

Description


FDMULE_APP_NAME




FDMULE_HOMEYes

Inputs

Input Name

Input Code

Required

Description

Mule Project PathFDMULE_PROJECT_PATHNoThis 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.portFDMULE_HTTP_PORTNo

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
${http.port} is used in your HTTP Connector.

Outputs

Output Name

Required

Description




Artifacts

This operation produces artifacts that will be stored in the artifacts repository.

Endpoint Selection

This operation will select all available endpoints associated to the environment/instance.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.


  • No labels