version 3.0

1. Certification Process

MuleSoft has expanded the Anypoint™ Connector platform enabling partners, from the MuleSoft Partner Program, and third-party development groups, to develop Anypoint™ connectors.

Every connector in the MuleSoft Anypoint™ Platform must go through a mandatory Certification Process before the final release. This certification process was conceived to assess the overall quality of all available connectors, ensuring that every connector published on the Anypoint™ Exchange follows industry best practices. As a result of this certification process, we are able to define a high quality threshold for every Anypoint™ connector available on the MuleSoft platform.

The scope of this process mainly depends on the composition of the connector, where a more complex connector will require further steps in the certification process. Our certification approach aims at testing every functional block of the connector prior to release.

This document first introduces the entire Connector Lifecycle Model, which includes four different stages: On-board, Development, Certification and Publishing.

  1. On-board: Takes into consideration the legal engagement between a third-party development group or partner, and MuleSoft.

  2. Development: The development stage, considering strictly testing methodologies.

  3. Certification: The certification process per-se, carried out by a MuleSoft.

  4. Publishing: Covering the final deployment of the certified connector within Anypoint Exchange.

The connector lifecycle model consists of the following stages:

connector lifecycle

1.1. Stage 1: On-Board

This first stage consists of legal matters involving the development of a connector for MuleSoft. This stage includes a learning phase of the default framework for developing connectors, the Anypoint™ Connector DevKit.

Both sides, MuleSoft and a partner/developer, state the guidelines and expected product deliverables before starting the development stage.

1.1.2. Learning Anypoint Connector DevKit

Anypoint Connector DevKit is the default tool for developing Anypoint connectors. It provides a vast set of features to help you develop and maintain your connector. Features include, but are not limited to:

  1. Visual design and implementation using Anypoint Studio with an Eclipse-oriented interface that simplifies and speeds up development.

  2. Maven support for development and building.

  3. Connector development and packaging tools.

  4. Authentication support for multiple types of authentication using OAuth and basic authentication types.

  5. DataSense support to acquire metadata in design time.

  6. Extensive testing capability.

  7. Examples, training, and support to ease startup.

  8. Batch, query pagination, and DataSense Query Language support.

The following are a set of useful links as a starting point:

1.2. Stage 2: Development

The development stage is one of two major phases, mostly occurring in the development team side. Since the MuleSoft team has relatively low control over this stage, MuleSoft requires every developer to follow a strict set of practices, which we call Mandatory Practices.

1.2.1. Design Specification Review

The design specification review phase, within the development stage, primarily assists developers and designers to clarify the functional behavior of the connector, provides extensive use cases, ranging from normal to border-cases, and includes an overall architecture design. MuleSoft strongly recommends that developers, as well as designers, consider this step mandatory, taking into consideration the Design Specification Template.

The Design Specification Template is one of the two Exit Criteria Documents from the development stage, needed by the MuleSoft team. The second document is the Certification Checklist Document, which ensures that every mandatory practice has been accomplished and complete all deliverables.

Due to Interoperability QA Guidelines, this checklist has the associated Manual Interoperability Test Run document.

1.2.2. Mandatory Practices

The Mandatory Practices assure an overall product quality, ranging from coding standards to documentation. The MuleSoft team requires that you strictly follow every practice and produce the required deliverables, including release notes and an user guide. Mandatory practices are detailed in following sections of this document.

1.3. Stage 3: Certification

The certification stage occurs mostly in the MuleSoft side. This stage includes different high-level objectives, such as:

  1. Automated code scan

  2. Manual code review and black box testing

  3. Manual and automated tests review

  4. Repository structure review

  5. Documentation review

  6. Runtime-compatibility review

  7. Static code analysis

The certification stage requires different prerequisites, because a wide set of code properties are checked and validated. These properties include GitHub credentials, Maven dependencies, and code versioning, among others.

1.3.1. Prerequisites

Prerequisites to be satisfied:

  • Design Specification Template Approved: The Design Specification template has been approved and all suggested corrections have been taken into consideration by the development team.

  • Source Code Access and Sandbox Credentials: As part of the certification process, the MuleSoft team internally runs and continues tests execution, and runs a set of code inspections to validate the quality of the connector. The following actions are required:

    • GitHub account with read access must be granted to the user connectors-cert-ci (connectors-cert-ci at mulesoft dot com).

    • If required, provide the sandbox credentials used for tests execution.

    • Create a release branch containing all the bug fixes produced during the certification process. This follows the naming convention "release/v<version-number>". After the certification process is complete, all changes are merged into the master branch and a tag, with all the changes, needs to be created. MuleSoft strongly recommends that you follow GitFlow branching practices.

  • Maven Dependencies:

    • The connector must be a final version: No SNAPSHOTS are allowed.

    • SNAPSHOT dependencies are not allowed.

    • External dependencies need to be located in well-known public repositories.

  • Presentation Demo: The objective of this demo is to go over the functional aspects of the connector, the overview of the system to be connected, and the underlying integration technologies (REST/SOAP/SDK). The audience of this meeting are Product Managers, Connectors Engineers, Leads, and QA staff.

  • Complete the Certification Checklist

  • Connector Documentation: Access to your connector documentation is required.

  • Versioning: The Connector must follow the following versioning scheme. Given a version number MAJOR.MINOR.PATCH, only increment a MAJOR version when you make incompatible API changes; increment a MINOR version when you add functionality in a backwards-compatible manner; and increment a PATCH version when you make backwards-compatible bug fixes.

  • License Terms: Please add the following legal terms above your license terms in

About MuleSoft Certified Connectors

MuleSoft Certified Connectors are developed by MuleSoft’s partners and developer community. These connectors have been reviewed and certified by MuleSoft. To purchase the [Connector Name] Connector or to receive assistance or support for it, please contact [Partner Name] directly at [Contact Information]. MuleSoft disclaims any support obligation for MuleSoft Certified Connectors.

By installing this connector, you consent to MuleSoft sharing your contact information with the developer of this connector so that you can receive more information about it directly from the developer.

Your license terms

1.3.2. Certification

After completing all previous steps, MuleSoft starts the certification process, which is an iterative process. MuleSoft reports different recommendations, which need to be completed by the connector development team, otherwise certification fails.

MuleSoft defines a tentative starting date for the certification process, where MuleSoft recommends that your team allocates different time windows, so as to respond to our recommendations. After you resolve and implement all requirements, the certification process ends. However, if there is no active engagement in solving the proposed recommendations within a seven-day period, the whole certification process is suspended and a new tentative starting date is defined.

MuleSoft provides a CloudBees dedicated account ( that you can use to monitor test execution and static code analysis reports.

The main communication channel between the MuleSoft team and your team is the MuleSoft DevKit forum, part of the MuleSoft forum community.

1.3.3. Results

  • Support Training: MuleSoft support team provides T1 support and helps you isolate the issue and identify if the issue is a MuleSoft issue or a connector issue.

  • Upload of certified connectors to Anypoint Exchange. After your connector passes certification, MuleSoft sends you an estimated date for when your connector will appear in Anypoint Exchange. As part of this process, the following information need to be provided:

    • High level description of the connector. The Salesforce connector can be used as a template example.

    • URL to release notes.

    • URL to functional documentation.

    • URL to Anypoint Connector DevKit generated documentation.

1.4. Stage 4: Publishing

The final stage in the connector lifecycle model is publishing, which MuleSoft carries out. After the certification process successfully completes, the connector deployes and publishes in the MuleSoft Anypoint Exchange.

1.5. Release Re-Certification

Mule ESB and Anypoint Studio have a release cycle of three month, where MuleSoft assures that previously published connectors are compatible with new releases. Due to class-loading issues and data-mapping problems, already published connectors might not work in new Mule ESB versions. Therefore, prior to Mule ESB and Anypoint Studio releases, MuleSoft runs regression tests to assure full forward compatibility.

If regression testing fails, it is up to the connector development team to decide whether the connector supports or not newer versions of Mule ESB and Anypoint Studio.

2. Coding Standards and Best Practices

Development best practices and coding standards have been included within the connector development community over time, leading to connector quality improvements. During the certification process, most of these practices and standards are checked by automated tools, such as SonarQube.

2.1. Anypoint™ Connector DevKit Version

The last version of Anypoint™ Connector DevKit must be used to develop your connector. As of May 2017, the latest stable DevKit version is 3.9.1.

DevKit 3.9.1 ensures that a connector will be compatible with Mule ESB 3.5.x, Mule ESB 3.6.x, Mule ESB 3.7.x and Mule ESB 3.8.x. However, external libraries employed by the connector might have conflicts with different Mule ESB versions. Sanity checks are mandatory for every Mule ESB version.

2.2. Connector Category

A connector should define its category in its POM properties:

<name>Mule Sample Connector </name>

  • For MuleSoft Certified Connectors (if you’re a partner building a connector, this is your connector’s category) DevKit 3.7.2 or above requires you to use Certified in the category.

  • For Select connectors, please use Select as the category.

  • For Premium connectors, please use Premium as the category.

Using this as a reference, please use <category></category> as the element for indicating the category.

All connectors except Community require that you include the @RequiresEnterpriseLicense attribute to the connector. In addition, if you are building a paid connector as a MuleSoft Certified connector, DevKit 3.8.0 or above supports license validation natively, but you can also use your own license validation mechanism and make sure that you enforce the legal use of your connector in the way you see fit.

MuleSoft will not be liable for errors in your code that could lead to people using your connector without a proper license.

For Select or MuleSoft Certified Connectors

@RequiresEnterpriseLicense(allowEval = true)
public class SalesforceConnector {

For Premium Connectors

@RequiresEnterpriseLicense(allowEval = true)
@RequiresEntitlement(name = "oracleebs-connector")
public class OracleEBSConnector {

2.2.1. Distribution Management

Configuration of the distributionManagement element varies from connector to connector, depending on its category and the project structure.

  1. Certified:

            <name>MuleEE Releases Repository</name>
            <name>MuleEE Snapshots Repository</name>
  2. Multi-Module Certified Connector:

    If a MuleSoft Certified connector is part of a multi-module project, before the release verify that:

    • The connector’s module is deployed to the private Nexus (same distribution management as described above for Standard, CI-releases).

    • The parent pom and other non-connector modules of the multi-module project have the same distribution management as described above for public or Community connectors.

For example, in a project with a parent pom, a utils module and a connector module, if and only if the connector is Certified, then the parent pom should declare the public distributionManagement, and then it should be overridden in the connectors' pom with the private distributionManagement.

2.3. Maven Conventions and Setup

The following section describes a set of conventions and best practices to follow when defining your connector’s Maven configuration.

2.3.1. Best Practices

A connector tested in an isolated environment might not work in a Mule environment. Therefore, different constraints apply:

  • Follow Maven default name conventions.

  • Do not overwrite or properties.

  • Do not reference SNAPSHOT dependencies in plugins or dependencies.

2.3.2. Do Not Define Custom Repositories

If your connector makes use of dependencies not available in standard Maven or MuleSoft repos, do not add additional repositories to pom.xml. Adding custom Maven repositories could cause several issues when the Mule application is mavenized. If you require this type of dependency, we will host the dependencies as part of you connector. As part of the hand-off for certification, these JARs need to be provided with all the required info such as groupId, artifactId and version.

2.3.3. Multi Module Layout

In large Maven projects, it is common practice to divide the project into submodules. This means you may end up with a module for your connector and other modules for utils, commons or other kinds of modularized source code that will be consumed by the connector.

Consider the following use case:

Project parent pom

<name>Mule Sample Connector Parent</name>


In your connector module’s pom.xml:

Connector sibling dependencies


It is important to note that your connector’s pom must inherit from certified-mule-connector-parent, and that each of the other sub-modules inherits from the project parent. Therefore, you will have artifacts inherited from the certified-mule-connector-parent pom and the connector pom:




Connector pom

<name>Mule Sample Connector</name>


This mix of pom inheritance and aggregation allows you to maintain a general parent pom for your secondary modules, to control the compilation from a single point, while providing the connector with the required devkit-parent pom, ensuring that all the other modules will be installed in your local repository before building the connector.

In multi-module projects, the deployment of the artifacts vary depending on the connector "category". Rule-of-thumb is that the parent pom and all the secondary modules (not the connector module) should be deployed to a public nexus repository, while the connector artifact will override its parent dependency management configuration with its own repository rules.

2.3.4. Avoid Caching

Connectors should not hold state, unless strictly necessary. Several APIs are actually hosted in cloud environments, and therefore caching states ends up exposing untrusted data in the connector. There are a few cases where the connector might need to save some data from the current API while working on it, which leads to caching.

For scenarios where the connector must use a cache, the following code should be used:

// 1) The connector asks for the manager of the Object Store
protected ObjectStoreManager objectStoreManager;

And then the objectStoreManager can get/create a custom Object Store as follow:

// 2) The connector asks Mule for the Object Store represented by a "given ID"
ObjectStore<? extends Serializable> os = objectStoreManager.getObjectStore("given ID");
// 3) The connector uses it"key", "value");

Another way to cache is to use temporary files, but it might depend on the use case.

2.3.5. Avoid Spawning Threads

Like caching, spawning threads within a connector is not recommended, since the common API lives in the cloud. This means that a connector will not improve its throughput with more threads, because every communication with the API means more HTTP requests/responses. Although we don’t recommend using threads, or caching, there may be custom cases requiring them.

For scenarios where the connector needs to spawn threads you should use a Executor Service.

2.3.6. Reading Resources From Within the Connector

When reading resources that are bundled with the connector, the usual getClass().getResourceAsStream("custom-file-to-read.txt") will work. But, if the file "custom-file-to-read.txt" can actually be parametrized through the Mule application, then there is another mechanism to use.

Consider that for your connector, a file can be fed from the src/main/resources folder (again, this file comes from Studio, not from the connector), the following code should be used:

// 1) The connector asks for the manager of the mule context
protected MuleContext muleContext;

which allows the resources to be read as follows:

ClassLoader classLoader = muleContext.getExecutionClassLoader();
URL resourceURL = classLoader.getResource("custom-file-to-read.txt");

Where "custom-file-to-read.txt" is the file to be read from the Mule app in src/main/resources/custom-file-to-read.txt.

2.3.7. Mule Dependencies

Adding dependencies to your connector should be carefully considered, since they might collide with Mule. A few constraints apply:

  1. When adding Mule artifacts, always use <scope>provided</scope>.

  2. When adding artifacts that might collide with Mule, choose versions that are in the current Mule versions, for what your connector is going to work with. Some of those artifacts are: cxf, jersey, spring, guava, etc.

2.3.8. Shading

For some corner cases, you might need to add a dependency that does collide with Mule either directly or in a transitive dependency. For those scenarios, we strongly recommend using the same version of the library as Mule does or, if possible, change your library to another equivalent. If none of the options above are available, and you still need that custom library that collides with Mule, then shading could work for you. Support for shading has been added in Devkit 3.5.3.

You need to modify your connector’s pom.xml file to add the shading plugin in order to achieve two things: 1) add the custom jar into the connector and 2) rename the packages of the library into a new one in order to avoid collisions.

For simple cases, were the colliding libraries are explicitly declared (for example, you require a different jersey version than the one packaged with Mule), shade only those dependencies.

The following snippet should work when using a library with the groupId org.some.library and the artifactId custom-artifact-id

        <version>${some.lib.version}</version> <!-- version to be included in the connector jar -->
        <!-- default scope is required-->

<!- rest of the configuration -->

                <!-- custom shade configuration -->

        <!-- Other plugins -->

Some other cases are more complex, since the issue appears with a transitive dependency. Let’s say you need an sdk my-sdk that uses some other dependency common-lib internally, and then if Mule uses an incompatible version of this common-lib, a classloader issue might result. For this case, you need to shade not only the sdk, but also the transitive dependency, that will now be explicitly declared as follows:

        <version>${some.lib.version}</version> <!-- version to be included in the connector jar -->
        <!-- default scope is required-->

        <version>${common.utils.version}</version> <!-- version used by the sdk -->
        <!-- default scope is required-->

                <!-- custom shade configuration -->
                    <!-- as a best practice, rename packages using the dependency version-->

Further explanation regarding the maven-shade-plugin can be found here.

2.3.9. Connector Structure

If you create your connector project using the DevKit Studio Plugin, the generated project directory layout is the recommended approach. If you are interested in more details, the project directory structure is described here.

In order to provide automated enforcement of these rules, the following plugin must be configured as part of the connectors pom.xml. We will be responsible for validating the project structure.

Copy and paste the following snippets into your connector pom.xml:


2.4. DevKit Standards and Best Practices

2.4.1. DataMapper Compliance

To have the best experience in Anypoint™ Studio, connectors must be DataMapper-compliant. To achieve this, all operations must follow these recommendations.

Any argument, returned or received, must be one of the following data types:

  • Map

  • POJO

  • List<Map>

  • List<String>

  • List<POJO>

  • List<List<String>>

These types must be part of the method signature so that DataMapper can auto-recognize the types in its mapping UI.


Only use a map if you cannot use a POJO.

Use a map only if your data:

  1. Is schema-less, for example if created using MongoDB.

  2. Has user customizable schemas, if created with Salesforce.

  3. Has unknown content.

Good Example Bad Example

List<Map> query()

List<DBObject> query

void send(Invoice invoice)

void send(Object object)

Invoice getInvoice(String id)

Object get(String id, Class typeToCreate)

All operations must have a single object to take input from DataMapper. The object must be a single object, not multiple arguments. This object is called the Primary argument.

Good Example Bad Example

void createInvoice(Invoice invoice)

createInvoice(Header header, List<LineItems> lineItems)

void upsert(List<Map> sobjects, String type, String externalFieldId)

N/A - Multiple arguments are still needed!

GetTaxResult getTax(TaxRequest request)

public GetTaxResult getTax(String companyCode, AvalaraDocumentType docType, @Optional String docCode, Date docDate, @Optional String salespersonCode, String customerCode, @Optional String customerUsageType, String discount, @Optional String purchaseOrderNo)

2.4.2. Java Version

A connector needs to define its target JDK version according to its compatibility with Mule runtimes. Mule runtimes 3.5.X must use Java 1.6, Mule runtimes 3.6.X must use Java 1.7, Mule runtimes 3.7.X must use Java 1.7 and Mule runtimes 3.8.X must use Java 1.7/1.8. This can be achieved by overwriting the POM property <jdk.version> with the desired version.

2.4.3. Annotations

If you have multiple arguments, annotate the Primary argument with:


This way DataMapper knows which argument in the operation to use for mapping.

2.4.4. No Warning During Compilation

DevKit does a intensive analysis of the used annotations and semantic of them in conjunction with others. It’s important the code is free of compilation warning to help on the maintainability of the code and to follow good practices.

2.4.5. DevKit Generated API Doc

Connector documentation is composed of two different types of documentation: DevKit Generated API Doc and the Connector Documentation.

DevKit API Doc is automatically generated by DevKit using the JavaDoc documentation in the connector class. This is one of the most important information sources used by the developer when using the connector.

2.4.6. Connector Code Convention

We provide a file with a recommended code styling format for connectors. This is an important aspect of the connector code quality and most of the connectors use this standard format. This style can be imported in Eclipse, Studio and IntelliJ.

Download the Connector Style Format here.

2.4.7. @Config Friendly Name Conventions

In order to provide consistency across all the connectors, Global Element default name should a follow a convention:

  1. If there is one single configuration, "Configuration" should be used as friendlyName

  2. If there is more than one configuration, the following convention should be followed:

    1. "OAuth 2.0" for OAuth configurations

    2. In other cases, use a brief description following the same terminology used in the system to integrate.

GlobalElement name is configured using the friendlyName attribute of the configuration class.

2.5. Connector Demo Example

A Mule application’s endpoints allow a user to interact with the service and API using the connector. Endpoints are committed to the GitHub repository along with source code. Use services or API use cases to determine which connector operations to select.

Guidelines to follow:

  • All demo projects must be isolated in a folder with a descriptive name (It does not matter if is just only one demo). Eg:

  • Use a meaningful name for the project. Avoid things such as "my-connector-demo" or "example-1". This name will be displayed in the ApiDoc site. Eg:

  • The demo name must have middle lines to separate the words in it and must be in lower case. example: "mail-service-demo"

  • Don’t add prefix such as "mule" or "app". Just the purpose of it.

  • Ensure that an app can be run by entering credentials without additional configuration or connector installation.

  • Use placeholders for credentials.

  • Ensure that flow names and message processors display names that make the use case easy to understand.

  • Provide instructions on how to run the app in a README file (for example, S3). It is recommended to add in a description of the demo application, such as what it aims to demonstrate and what each step of the demo is responsible for. Where application, you can also mention where your demo fits in a larger use case.

  • Expose a set of endpoints that the user can access following the steps in the README to reproduce a use case.

  • Consider implementing a CRUD (or similar) use case with chained processors whose payloads get logged into the Studio console (for example, S3).

  • Use DataWeave for Premium, Select or MuleSoft Certified connectors' CRUD (or a similar) use case if API methods attributes and/or return types allow it.

  • Consider basic error handling in the Mule app.

There are two kinds of demos that you can create:

  • Single operation demos

  • Workflow demos

Single operation demos are used to invoke just one operation in the connector. Workflow demos are used to invoke a number of operations in the connector sequentially. These aim to show a simple usecase of the connector, such as a normal CRUD workflow. We provide two templates to help you create an interface for your demo, one for each kind of demo. You can find the template for single operation demos here and the template for the workflow demos here.

The demo HTML pages above make use of Twitter Bootstrap to present a clean interface to the user. You should base your demo on this template. If you are not familiar with the Twitter Bootstrap library, it is highly suggested to look at their documentation page. Single operation demos only provide a form, whereas workflow demos provide an accordion, where one step leads to the next. In the latter case, any values retrieved by the first step should be used to autofill values in the second step where possible.

As an example, let us take a CRUD workflow for a number of Twitter API calls. The first step will create a tweet and return a number of values pertaining to the tweet that was created. One of these values would be the Tweet ID. The second step would be the "read" operation. The tweet ID should be automatically filled in the second step so that the user is simply able to submit a "read" API call without any needed input. The final step of the workflow should present an alert (or a notification of some sort), that the workflow has ended, outputting any relevant information from the last step. An example of this would be a "Tweet Deleted" message if the workflow was completed successfully, and the tweet that was created in the first step is successfully removed.

The following code snippets explain some parts of the above HTML page. The demo contains 3 parts:

  • The JavaScript that handles asynchronous calls to the demo running on a Mule instance.

  • The CSS that renders the HTML page

  • The HTML itself

The JavaScript

The JavaScript for this demo is simply used to send AJAX calls to a Mule server that hosts your demo application. In the case of workflow demos, it is also used to collapse the accordions as the user goes from one step to the next.

Initially, a reference to the <div> and <form> elements is obtained.

var createDiv   = $('#createDiv');
var readDiv     = $('#readDiv');
var updateDiv   = $('#updateDiv');
var deleteDiv   = $('#deleteDiv');

var createForm  = $('#createForm');
var readForm    = $('#readForm');
var updateForm  = $('#updateForm');
var deleteForm  = $('#deleteForm');

Then, each form is paired with a jQuery function sends an AJAX request whenever a form is submitted.

createForm.submit(function() {
    type: 'POST',                             // Submit an HTTP POST request
    url: '/create',                           // The URL where your endpoint is listening
    data: createForm.serialize(),             // Serialized form URL-encoded input
    success: function(data) {                 // Success function called if request succeeds

      $('input[name=message]').val(data.message); // Autofill data in the next workflow step as needed

      createDiv.collapse('hide');             // Hide current accordion window
      readDiv.collapse('show');               // Show next accordion window
    error: function(request, status, error){  // Error function is executed if an exception occurs in the flow
      alert(request.responseText);            // Alert the user of any errors

  return false;                               // Let jQuery handle the form submission

In the case of a workflow demo, every form will represent a step in the workflow. The above code snippet should be repeated for every form you have in your workflow, applying changes as needed.


The HTML page linked above comes with a number of CSS presets that you can use throughout your demo. A number of Bootstrap CSS classes are also used to build the accordion and the panels within it. For more information on how to build your own accordion, or even extend the one in the HTML template, please refer to the Bootstrap Accordion documentation page.


This part is what ties everything together. The HTML represents what your users will see when they open your demo to use your connector. Take this HTML snippet as an example:

<div class="panel-group" id="accordion">
    <div class="panel panel-default">
        <div class="panel-heading">
            <h2 class="panel-title demo-heading">
                <a data-toggle="collapse" data-parent="#accordion" href="#createDiv">Create</a>
        <div id="createDiv" class="panel-collapse collapse in">
            <div class="panel-body">
                <form id="createForm" class="demo-form" role="form" >
                    <input type="text" name="message" value="Hello from Mule!" required class="form-control" ><br>
                    <input class="btn btn-lg btn-primary btn-block" type="submit" value="Create"><br>

The above snippet of HTML is taken from the workflow demo template, it represents a single panel in the accordion. This panel is split into two parts: the header and the content. The header refers to the content through the anchor tag (<a>). When this header is clicked, the content is shown. On the other hand, the content is composed of a simple form that is used to submit requests to Mule. These requests are handled by the JavaScript shown above.

For a complete example of a workflow demo, you can download a sample project that uses MongoDB here.

2.6. Third-Party Licenses

As part of the certification, it’s important to validate that all the libraries used by the connector are Open Source friendly. A easy way to generated a report of this, is running the following command:

mvn org.codehaus.mojo:license-maven-plugin:1.8:aggregate-add-third-party

The current list of licenses approved for use by third-party code redistributed with Community Connector projects is:

  • Apache Software License 1.1

  • Apache Software License 2.0

  • W3C Software License

  • Common Public License Version 1.0

  • IBM Public License 1.0

  • Mozilla Public License Version 1.1

  • Common Development and Distribution License (CDDL) Version 1.0

  • GNU Free Documentation License Version 1.3

  • BSD

  • MIT

Licenses that are not approved for use include:

  • GNU GPL 2.0


  • Sun Binary Code License Agreement

2.6.1. Open Source Compliance Checklist

Check that :

  • No not approved for use third-party libraries are been distributed with your project

  • There are no dependencies with no license

  • Approved third-party are compliant with their license requirements

2.7. Connector Icon

We recommend your connector have a consistent look-and-feel with existing connectors in Anypoint Studio. You can replace existing icons in {your connector project}/icons with proper ones. With DevKit 3.9.0, connector can properly show icons in line with the new Studio theme. Please follow the examples for your connector icons.

Example: Redis Connector

Icon Directories

directories for icons
Figure 1. New Icon Directories

Classic Icons for the old Studio theme

redis connector large
Figure 2. Redis Connector Large Icon (48x32)
redis connector small
Figure 3. Redis Connector Small Icon (24x16)
redis endpoint large
Figure 4. Redis Endpoint Large Icon (48x32)
redis endpoint small
Figure 5. Redis Endpoint Small Icon (24x16)

Light Icons for the new Studio theme

redis connector large
Figure 6. Redis Connector Large Icon (26x26)
redis connector small
Figure 7. Redis Connector Small Icon (16x16)
redis endpoint large
Figure 8. Redis Endpoint Large Icon (26x26)
redis endpoint small
Figure 9. Redis Endpoint Small Icon (16x16)


DevKit requires that your source files contain a license header. To apply the license header to every source file in your project, run the following command in a command console at the root of your project, which contains your connector project’s pom.xml file:

mvn license:format

Example: LICENSE_HEADER.txt for MuleSoft Salesforce Connector

(c) 2003-2016 MuleSoft, Inc. The software in this package is published under the terms of the Commercial Free Software license V.1, a copy of which has been included with this distribution in the file.

3. Static Code Analysis and Coverage

Most automatic validations on your connector’s code are done with SonarQube, an open source static code analysis tool that helps developers identify hot spots in code, bad code quality, technical debt, as well as define a number of other issues. To release a connector, you must fix blocker and critical issues.

To perform these validations yourself, install and configure a the SonarQube server that we provide with rules specific to the certification process. If you are certifying multiple connectors, you can reuse the same server.

For guidelines on how to build your tests using this framework, see Automated Functional Testing

3.1. Installing SonarQube

The quickest way to get SonarQube up and running is to install it locally with an embedded database. If you wish to use a standalone database or a more advanced configuration, see the related SonarQube Eclipse Plugin Setup documentation.

You need a server running Oracle JRE 6 or higher. (OpenJRE or other distributions are not supported by SonarQube.)

  1. Download and extract the latest version of SonarQube(all platforms).

  2. Run <installDir>/bin/<yourOS>/ start or <installDir>\bin\<yourOS>\StartSonar.bat if on Windows. The server might take a while to start even after the “Started SonarQube” message appears.

  3. Browse to http://localhost:9000.

  4. Log in with the following credentials:

    1. Username: admin

    2. Password: admin

  5. Download our Custom Quality Profile

  6. Go to the Quality Profiles tab and Click Create.

  7. Then choose the Quality Profile file that you downloaded, name it "Anypoint Connectors Profile" and click Create.

  8. When you see the profile in the list click in Set as Default.

  9. Finally you need to set the exclusions, to set this go to Settings and click Exclusions.

  10. In the Code Coverage tab add target/**

  11. Click Add Value and click Save Code Coverage Settings.

  12. In the Files tab add target/** under Global Source File Exclusions and Global Test File Exclusions.

  13. Finally, click Add Value in both and click Save Files Settings.

sonar 01

3.2. Performing Your First Analysis

For the first run of your project, go to the project’s root folder and run:

mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent test
	-Dmaven.test.failure.ignore=true -Dtest="*TestSuite,*Test"
	&& mvn install && mvn sonar:sonar

mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent
	install-Dmaven.test.failure.ignore=true && mvn sonar:sonar

This creates the project in your sonar installation, allowing you to use the Eclipse SonarQube plugin from inside your Anypoint™ Studio. Using this plugin is the recommended way, but is always possible to run the inspections manually with * mvn sonar:sonar *.

If you are experiencing false positive issues, you can disable the inspection using //NOSONAR comment at the end of a line which has the issue on a case-by-case basis. Every use of //NOSONAR is recorded by SonarQube as an Info issue so you can track its usage in your connector’s code.

The use of //NOSONAR comments should only be used when there is full certainty that this inspection is a false positive.

For example, suppose you have an incorrectly capitalized method that you can’t change. This is normally a blocker issue:

sonar 1

After adding the //NOSONAR marker, this is no longer a blocker issue, but is marked as Info so you can track the usage of //NOSONAR throughout your project:

sonar 2

3.3. SonarQube Eclipse Plugin Setup

  • Open Anypoint™ Studio, then select Help > Install New Software.

    sonar 3
  • In the Work with text box, fill in the update site URL: SonarQube Integration for Eclipse (update-site) -

    sonar 4
  • Check the SonarQube Java option.

  • After completing the installation, restart Anypoint™ Studio.

  • Open Anypoint™ Studio’s preferences, and browse to the SonarQube section. Expand it, and select the Servers subsection. Click Add and fill in the URL and credentials for your server (by default, admin/admin).

    sonar 5

    Click the Test connection button to ensure that your settings are correct.

  • To associate your project on the SonarQube server, perform a full analysis once. You can do this by running mvn sonar:sonar in your Connector project.

    You should perform this full analysis from a machine that is on the same network as the SonarQube database, otherwise it might take very long to complete.

    When your project finishes analyzing, in Studio right-click your connector project and click Configure > Associate with SonarQube. Because your project was analyzed with Maven, the association detects automatically.

    sonar 6
  • After association, your project is analyzed with SonarQube and the results are shown on the SonarQube issues tab. Also, the Package Explorer and file editor display error and warning icons according to the issues on your project.

    New issues introduced since the previous analysis are marked as errors, while existing issues are marked as warnings. This is a cosmetic difference only, which helps to highlight new technical debt being introduced in your code before you check it in.

  • To analyse your project again, right-click it and click SonarQube > Analyse.

3.4. Quality Profile Rules

SonarQube classifies each issue with a severity:

  • Blocker & Critical: Bugs or unacceptable programming practices. Your connector cannot have blocker or Critical issues to be certified. You must correct all issues.

  • Major: These inspections fall in a similar category to the critical issues but with lower priority.

  • Minor: Correctness, clarity or performance issues that do not impact your connector’s functionality significantly.

  • Info: Keeps track of useful information that might otherwise go unnoticed.

To see the full list of rules checked by SonarQube, browse to the Anypoint™ Connectors Certification quality profile through the web UI.

3.5. Code Coverage

SonarQube also lets you manage Code Coverage reports of your connector.

Generate a code coverage report in SonarQube with this command:

mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent install
	-Dmaven.test.failure.ignore=true && mvn sonar:sonar

After this command finishes executing, Sonar displays a report with the name of your connector. For example, this screenshot shows the Salesforce connector’s Sonar report after running every Unit test and Functional test:

coverage guidelines 1

Delving further into the project details shows you a code coverage percentage on a per-class basis.

coverage guidelines 2

Delving even further, it shows you the exact lines that are covered by tests and those that are not.

coverage guidelines 3

Every connector method must have unit or automation tests. A connector fails certification if it does not have all its message processors, message sources, and custom transformers covered by unit tests or automation tests. Also, all the utility classes that are part of a connector must have a high level of code coverage.

3.5.1. Code coverage must be no less than 70%.

Testing your processors gives you a good indication of the quality of your connector. When you build automation tests, you are using your own connector to connect to an API. If you find it hard to test all cases of a message processor, then consider separating your message processors into smaller ones, if possible.

If your connector bases its processing around metadata, test every possible metadata entry that the API supports. As an example, the Salesforce connector supports multiple SFDC objects (such as Account, Contact, Lead etc.), but it only contains one “create” operation. Create a unit test for every metadata object to ensure proper compatibility with the message processor.

3.5.2. Ignoring Classes from Testing

You should NEVER prevent classes from being tested unless there is good reason. If you feel that there is a need to ignore classes from inspection, contact either Mariano Quintela, or Paulo Gustavo Veiga. Unless explicitly stated in the code comments or in some form of internal documentation, assume that all code must be inspected. Any ignored classes or packages without proper explanation should be inspected and any blocker or critical issues that arise should be resolved, and tested by the developer before the connector is released.

There are a number of ways of ignoring classes that you do not want inspected by SonarQube:

  • Method level ignore:

    • Methods can be ignored by adding a //NOSONAR comment next to the method declaration. Example:

      public void someMethodToNotInspect() { //NOSONAR
  • Class level ignore

    • It may be the case that whole classes need to be ignored because they’re not in the control of the developer. As an example, the SFDC Connector contains classes from the SFDC JAR. These had to be modified slightly to include no-args constructors for DataSense reasons. As a result, these classes have to be ignored since the code quality is not in control of the SFDC Connector developer.

    • Classes can be completely ignored by adding // NOSONAR next to the class level definition. Example:

      public class MyClassThatShouldntBeInspected { // NOSONAR
  • Package level ignore

    • Whole packages can be ignored by adding the “sonar.exclusions” property inside the pom.xml file. Example:


      This ignores any file under the com.sforce package under src/main/java.

3.6. Code Quality Review Guideline

This is a hard area to tackle because typically, the person running certification is different from the one implementing the connector and writing tests for it. As a result, you might inspect the code and be completely lost.

If code documentation is not sufficient, point this out to the developer and PM.

As you try to understand the code, you might run into certain code pieces that you’re not sure why they’re there. As an example, PeopleSoft contained synchronous code and some time was spent by the developer understanding why they were there. It turns out that they were not needed, and were causing a degree of locking when working with concurrent requests. If you think that there are code blocks that feel out of place, mention it to the developer or PM.

4. Tests Automation

This section explains how to automate test cases for Anypoint MuleSoft Connectors. Tests can be either integration tests or unit tests depending which aspect of the connector is being tested.

Integration tests at testing the interaction between the code and an external system. These tests allow to verify aspects such as the validity of credentials, different connection configurations or the entire processor operation. Hence, a Mule runtime environment is provided, thus assuring backward and forward compatibility. Unit tests aim at verifying isolated components of the connector which do not require neither a valid connection nor a Mule runtime.

Once all tests have been engineered, a final test execution step is required. This execution step requires to run functional tests with different Mule runtimes configurations, run System tests with valid/invalid credentials and finally run unit tests.

4.1. How to Start?

There are different aspects to tests:

  1. Processors: for each processor, an integration test is required.

  2. MetaData: MetaData requires functional tests as well, but employing a slightly different approach than processors.

  3. Pagination: if the connector implements @Paged processors, then pagination has to be tested.

  4. Test Connectivity: every connection configuration has to be tested with valid/invalid credentials, wrong configuration values, etc.

  5. WSDL Operations: testing WSDL operations is required ONLY when your connector is SOAP Connect. As with MetaData, testing these kind of operations require a different approach than processors.

4.2. Best Practices

Before starting, there are a few best practices when engineering test cases:

  1. Always clean the connector sandbox after running either Functional or System tests.

  2. setup(): if @Before behavior is required, this method must be defined and annotated accordingly.

  3. tearDown(): if @After behavior is required, this method must be defined and annotated accordingly. Normally all cleaning behaviour regarding the sandbox should go here.

  4. .gitignore: automations credentials and any sensitive data should be added to this file to avoid versioning them.

4.3. Integration tests

Integration tests aim at assuring the correct behavior of the connector with external systems. These can make use of a provided Mule runtime environment, for testing the integration with the Mule architecture.

These tests are mandatory within the certification process, and need to be carried out following strict practices, who are detailed throughout this section.

4.3.1. Tests organization

Integration tests need to be organized as follows:

  1. Naming convention: integration test classes must end with IT. Alternatives ending names are discouraged, and will require a special configuration for them to be run.

  2. Test suites and Test Categories might be used if needed, although are discouraged.

  3. The following package organization is encouraged:

    • org.mule.modules.<connector-project>.automation.functional for integration tests that make use of the Connector Testing Framework.

    • org.mule.modules.<connector-project>.automation.system for all those tests that require a connection but do not use CTF.

4.3.2. Test Data

Test data must be contained within a org.mule.modules.<connector-project> class. This test data builder must generate all necessary test data for every single functional test. Developers are free to use whatever data input techniques within this data builder (JSON, Beans, etc.).

It is advisable to avoid binding test data with test cases and keep all test data generation within the test data builder.

4.3.3. Connector Testing Framework

The main objective is to test the connector with different Mule runtime environments through the Connector Testing Framework, allowing to detect possible conflicts, such as class loading issues. The default functional testing framework is called CTF (Connector Testing Framework). Documentation of CTF is available here

This framework eases the creation of connector functional tests, where the developer is not necessarily involved with Mule’s internals, such as flows, configurations and Spring beans. The objective of this framework is twofold. On the one hand, we decouple how Mule works and how functional tests are written. On the other hand, we enable a runtime platform to run connector tests with multiple Mule versions by executing the tests in remote Mule instances, achieving a decoupled runtime environment.

Any other approach for carrying out functional tests is highly discouraged. However, certain aspects of functional testing is not covered within CTF and thus custom approaches might be used. The following sections described which aspects can and can not be tested with CTF.

4.3.4. CTF Components

All functional test cases classes must extend from a AbstractTestCase<T>, which is parametrized with the connector type under tests.

AbstractTestCase<T>.java is found within Extending from this class is mandatory, since it assures the correct use of the CTF as it implements all the initialization and shut down of the framework.

Every test case needs to be named as <OperationName>IT. This naming convention provide a uniform template for all connectors in the Mule ecosystem, and allows the framework to run on the validate Maven phase.

<OperationName>IT class

Each connector processor must have an associated <OperationName> class that contains its related test cases.

package org.mule.modules.<connector-project>.automation.functional;

import ...

public class <OperationName>IT extends <<ConnectorClass>>AbstractTestCase {

   // Private attributes used as auxiliary fields for storing test run values.
   private Integer leadRecordId;

   // Use to create required data for the test.
   public void setUp() throws Exception {

   // Returns the sandbox to its original state.
   public void tearDown() throws Exception {

   // Method that invokes the connector operation under test and asserts on the return value.
   public void <testName> throws Exception {
     // Test code
     // Assertions

The exception might be managed within the test case if the required information is available or it might be thrown.

[ConnectorClass]AbstractTestCase class

In case a sub-parent is needed, it must be named as [ConnectorClass]AbstractTestCase, which will extend from CTF AbstractTestCase and add the required behavior, such as @Before and @After methods.

import ...

class <<ConnectorClassName>>AbtractTestCases extends AbstractTestCase<ConnectorClass> {

   public <<ConnectorClassName>>AbtractTestCases(){
     // This is required if running single tests as well as a test suite.

   public void setUp() throws Exception {

   public void tearDown() throws Exception {
CTF connector and dispatcher

The AbstractTestCase class provides getters for the following objects:

  1. Connector: this CTF component enables testing on every connector processor, mocking the real connector under tests. Thus, all the underlying Mule logic is kept within CTF and not exposed to the test developer.

  2. Dispatcher: this second CTF component enables testing on particular aspects of a connector, such as pagination, WSDL operations and MetaData.

Both objects are properly documented within CTF documentation here.

4.3.5. Topics to test

The integration tests should cover the following:

  1. Processors

  2. MetaData

  3. WSDL Operations

  4. Pagination

  5. Sources

  6. Test Connectivity:

We will use throughout these examples the CookBook Connector, a test connector available here. We will not consider a <ConnectorName>TestCase and therefore every test case will extend directly from AbstractTestCase.
Testing processors

CTF enables testing of processors in a simple manner. By means of a mocked connector, we can call every connector operation with its actual parameters, without dealing with Mule internals (Spring beans, Mule flows, etc.).

Let’s consider one of the available processors within CookBook Connector, getRecentlyAdded. A functional test will be:

package org.mule.modules.cookbook.automation.functional;

import ...

public class GetRecentlyAddedIT extends AbstractTestCase<CookBookConnector> {

    // No @Before or @After methods required.

        public void testGetRecentlyAdded() throws Exception{
        List<Recipe> resultList = getConnector().getRecentlyAdded();
        // Assert on resultList.

The method getConnector() returns an instance of the actual connector under test, allowing to invoke its operations with its parameters. In this particular case, getRecentlyAdded does not require any parameters.

Testing MetaData

Anypoint Studio DataSense allows a connector to gather metadata from the remote service in design time, enabling Anypoint developers to deal with actual object types and descriptions instead of generic types.

A single metadata class per MetaDataCategory is accepted, named as <CategoryName>MetaDataIT, which will include two tests: testMetaDataKeys and testMetaData for that specific category. CTF provides getDispatcher(), which exposes two methods for fetching MetaDataKeys and MetaData, fetchMetaDataKeys() and fetchMetaData(keyName). The first one fetches all keys from the MetaData underlying service, while the second one retrieves the descriptor for a particular MetadataKey.

package org.mule.modules.cookbook.automation.functional;

import ...

public class CookBookMetadataCategoryMetaDataIT extends AbstractTestCase<CookBookConnector> {

        public void testMetaDataKeys() throws Exception{

        Result<List<MetaDataKey>> metaDataKeysResult = dispatcher.fetchMetaDataKeys();

        List<MetaDataKey> metaDataKeys = metaDataKeysResult.get();

        MetaDataKey recipeKey;
        MetaDataKey ingredientKey;

            for (MetaDataKey key : metaDataKeys) {
                    if (recipeKey == null && key.getId().equals("Recipe"))
                            recipeKey = key;
                    if (ingredientKey == null && key.getId().equals("Ingredient"))
                            ingredientKey = key;

        //Assert on MetaDataKeys

        public void testMetaData() throws Exception{

            Result<List<MetaDataKey>> metaDataKeysResult = dispatcher.fetchMetaDataKeys();

        List<MetaDataKey> metaDataKeys = metaDataKeysResult.get();

        MetaDataKey recipeKey;
        MetaDataKey ingredientKey;

            for (MetaDataKey key : metaDataKeys) {
                    if (recipeKey == null && key.getId().equals("Recipe"))
                            recipeKey = key;
                    if (ingredientKey == null && key.getId().equals("Ingredient"))
                            ingredientKey = key;

        //Asserts on MetaData
            Result<MetaData> recipeKeyResult = dispatcher.fetchMetaData(recipeKey);

        Result<MetaData> ingredientKeyResult = dispatcher.fetchMetaData(ingredientKey);
All metadata tests need to be annotated with @MetaDataTest. This assures that metadata tests are only executed in the latest Mule Runtime.
Testing MetaData: preferred testing approach for complex domains

When the domain of the connector is complex and its entities contain large and deep object structures, MetaData tests might end up being long, complicated to read and they might not even test the entire MetaData description.

To deal with this scenario, the following approach is highly recommended:

  1. Naming conventions is maintained, where a single metadata class per MetaDataCategory is accepted, named as <CategoryName>MetaDataIT.

  2. A MetaData abstract parent is introduced, named as available within CTF packages. This method need to be parametrized with the connector class.

  3. Every <CategoryName>MetaDataIT need to extend from AbstractMetaDataTestCase and defines which keys/entities must be tested as follows:

package org.mule.modules.cookbook.automation.functional;

import ...
import java.util.ArrayList;
import java.util.List;

public class CookBookMetaDataCategoryMetaDataIT extends AbstractMetaDataTestCase<CookBookConnector> {

    private static final List<String> keys = new ArrayList<String>();

    static {

    public <CategoryName>MetaDataTestCases() {
        super(keys, CookBookMetaDataCategory.class, CookBook.class);

Thus, every metadata test case defines within its category the important entities to test. The underlying implementation will only tests those categories and compare the results of the MetaData retrieved from the sandbox with JSON-based structures kept within the connector test resources. These structures are created the first time the test is ran and kept afterwards for future test executions.

Testing WSDL Operation

Testing WSDL operations is easily supported by CTF. WSDL operations consume WSDL files mapped as XMLStreamReader files, which must be generated within the TestDataBuilder as usual.

Testing WSDL operations is only required when the connector under test is a SOAP Connect-based connector, opposite to an SDK-based connector.

A single WSDL test case is accepted and need to be named as WSDLTestCases. Since WSDL testing consume WSDL files, they must be organized as follows:

  1. src/test/resources/payloads.xml: A directory that must contain all required WSDL/XML files, which are consumed by the TestDataBuilder.

  2. WSDL_ID#Operation: Every WSDL/XML file must be named as the WSDL ID following the separator # and ending with the operation name.

Testing WSDL operations is supported by means of the following method:

package org.mule.modules.cookbook.automation.functional;

import ...

public class WSDLTestCases extends AbstractTestCase<CookBookConnector> {

    public void testWSDL<OperationName>() throws Exception {

        XMLStreamReader request = TestDataBuilder.getXMLStreamReaderForAParticularWSDL();

        ConnectorDispatcher<CookBookConnector> dispatcher = getDispatcher();

        XMLStreamReader XMLStreamResult = dispatcher.invokeWsdlOperation(request, "<WSDL_ID>", "<OperationName>");

        // Asserts on XMLStreamResult

This is a simple example illustrating how CTF supports WSDL operations with a single method. The first parameter is the XMLStreamReader input based on a specific WSDL/XML. The second argument is the WSDL_ID to be used, while the last one stands for the operation name. If your connector does not include multiple service definitions, you need to opt for using the variant of the method without the WSDL_ID as follows:

package org.mule.modules.cookbook.automation.functional;

import ...

public class WSDLIT extends AbstractTestCase<CookBookConnector> {

    public void testWSDL<OperationName>() throws Exception {

        XMLStreamReader request = TestDataBuilder.getXMLStreamReaderForAParticularTest();

        ConnectorDispatcher<CookBookConnector> dispatcher = getDispatcher();

        XMLStreamReader XMLStreamResult = dispatcher.invokeWsdlOperation(request, "<OperationName>");

        // Asserts on XMLStreamResult
Testing @Paginated methods

A connector method can be annotated as @Paged, which means that when calling that method, several calls to the underlying API will be generated so as to avoid retrieving a possible big set of results in one API call. As a result, the user will consume the entire set of results with a single call to the method, although Mule will automatically generate different API calls.

Let’s consider the queryPaginated(..) method within the CookBook connector, which is annotated as @Paged and defined as:

    @ReconnectOn(exceptions = { SessionExpiredException.class })
    public ProviderAwarePagingDelegate<Map<String, Object>, CookbookConnector> queryPaginated(
           final String query, final PagingConfiguration pagingConfiguration)
           throws SessionExpiredException {
       return new CookbookPagingDelegate(query, pagingConfiguration.getFetchSize());

In order to test this paginated, CTF enables the following mechanism:

package org.mule.modules.cookbook.automation.functional;

import ...

public class QueryPaginatedIT extends AbstractTestCase<CookBookConnector> {

    //No @Before or @After methods required

    public void testQueryPaginated() throws Exception {
        Object[] args = new Object[] { "SELECT Id FROM Recipes", null };

        Collection<Map<String, Object>> listResult = (Collection<Map<String, Object>>) dispatcher.runPaginatedMethod("queryPaginated", args);

        // Assert on listResult

This test extract illustrates how pagination works. If we try to execute connector.queryPaginated(…​), a runtime exception UnsupportedMethodAnnotationException will be thrown by CTF. We need to used the dispatcher instead, which exposes a runPaginatedMethod(methodName, args). The first parameter is the method name (camel-like), while the second is the list of parameter taken by the method in the same order as defined in its signature. In this case the first parameter is the query itself, while the last parameter, a PagingConfiguration object, is not present.

We provide a mechanism to test operations annotated with @Paged, which indirectly tests the underlying pagination mechanism. However, testing how the pagination mechanisms works, i.e. testing the number of pages retrieved and the values within each page should not be performed with the testing framework, since most likely it is a unit test and not a functional test.
Testing Sources

CTF provides a simple approach to test source operations within a connector. The dispatcher provides three methods: initializeSource, getSourceMessages and shutDownSource. The following example introduces source testing with CTF, considering a simply source implementation as follows:

    @Source(sourceStrategy = SourceStrategy.POLLING, pollingPeriod = 1000)
    public void retrieveEvents(final SourceCallback sourceCallback, String message) throws Exception {

The following test case depicts how CTF enables source testing:

package org.mule.modules.automation.functional;

import java.util.List;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import org.mule.modules.automation.TestConnectorAbstractTestCase;
import static org.junit.Assert.*;

public class SourceIT extends TestConnectorAbstractTestCase {

        private String testMessage;

        public void setUp() throws Exception {
                testMessage = "testMessage";
                Object[] signature = {null, testMessage};
                getDispatcher().initializeSource("retrieveEvents", signature);

        public void testSource() {
                List<Object> events = getDispatcher().getSourceMessages("retrieveEvents");

        public void tearDown() throws Exception {

To test a particular source, we need to initialize it first by means of its name and the array of parameters, similar as testing @Paged operations. It is important to consider that the SourceCallback parameter, which is mandatory when implementing a source, must be set to null in the array of parameters.

Once the source has been initialized, it will start receiving messages. These messages will be store by the CTF. The dispatcher allows to retrieve these messages to further assert whether a particular message has been received by the source or not. Finally, the source needs to be properly shutdown using the dispatcher as shown.

It’s important to notice that once the source has been initialized, it will start gathering events. However, if the remote endpoint takes time to produce those messages, it is a good idea to explicitly wait an amount of time before gathering the received messages with getDispatcher().getSourceMessages(…​).

Test Connectivity

These tests aim at testing the logic under the @TestConnectivity annotated method by covering the internal logic of the method itself, which differs from testing the annotation used. A single test case is accepted for each connection configuration, named as <ConfigName>IT, which will contains as many tests as set of credentials are used. As the connectivity tests don’t require the use of the CTF, they should be placed in the org.mule.modules.<connector-project>.automation.system package.

To do so, let’s consider the following connector example and its connection configuration.

@ConnectionManagement(friendlyName="CookBookConnector Basic Connection", configElementNam="config")
public class CookBookBasicConfig {

    public void connect(@ConnectionKey String username, @Password String password){

    public void testConnectivity(@ConnectionKey String username, @Password String password){
        // Always call the connect method somewhere within the @TestConnectivity method
        this.connect(username, password);

        // Add extra behavior when testing the connection

In order to test this connection config, the following test is required:

public class CookBookBasicConfigTestCases {

    private Properties validCredentials;

    private static final Logger logger = Logger.getLogger(CookBookBasicConfigTestCases.class);

    public void setup(){
        validCredentials = ConfigurationUtils.getAutomationCredentialsProperties();

    public void validCredentialsConnectivityTest throws Exception {
        // Add required extra behavior here if necessary.

        final CookBookBasicConfig config = new CookBookBasicConfig();

        String username = validCredentials.getProperty("config.username");
        String password = validCredentials.getProperty("config.password");

        // Call the @TestConnectivity.
        config.testConnectivity(username, password);

    public void invalidCredentialsConnectivityTest throws Exception {
        // Add required extra behavior here if necessary.

        CookBookBasicConfig config = new CookBookBasicConfig();

        // Call the @TestConnectivity.
        config.testConnectivity("noUserName", "noPassword");

    public void nullCredentialsConnectivityTest throws Exception {
        // Add required extra behavior here if necessary.

        CookBookBasicConfig config = new CookBookBasicConfig();

        // Call the @TestConnectivity.
        config.testConnectivity(null, null);

Note that in this case, the file is formed by <configName>.<placeholder>=<value>. In this example we have as config name (defined by configElementName paramenter) cookbookconfig. This file always goes within src/test/resources.

The valid credentials need to be the same as with the functional tests, in this case

Connectivity tests need to tests as many scenarios as possible, such as invalid credentials, null parameters, etc.

ConfigurationUtils.Java class is available within CTF packages.

4.4. Unit Tests (optional)

Unit tests aim at assuring the correct behavior of a particular code unit within the connector. Although not a mandatory step within the certification process, different aspects require unit tests instead of functional tests.

4.4.1. Test Organization

Unit tests need to be engineered and organized as follows:

  1. Naming convention: unit tests should follow JUnit naming conventions, normally ending with Test or TestCase. Any other ending will produce the Maven Surfire plugin to skip these tests during installation.

  2. Test suites and Test categories are not required for unit tests.

4.4.2. Packages and files

Test files need to be kept in specific packages as follows:

  1. org.mule.modules.<connector-project>.automation.unit contains the unit test cases exclusively.

Overriding package organization is only accepted if a unit test need to be contained within the same package of the class under tests, i.e. when the class has package visibility.

4.5. Test execution

Once all tests have been engineered, they must be executed following a few guidelines:

  1. Integration Tests:

    • Test that use the CTF (functional tests) must be executed with different Mule runtime environments, assuring the correct integration of the connector with older and current Mule runtimes.

    • Connectivity tests need to be executed with valid and invalid credentials, covering both success and error cases.

  2. Unit Tests: all unit tests need to be run with mvn test.

The whole set of test can be executed as mvn verify.

mvn test must only run unit tests, since the remaining tests (Functional and System tests) need a valid connection and credentials. Without these credentials, tests will fail.

4.5.1. Running Functional Tests

The overall idea of functional tests is to ensure backward and forward compatibility in every aspect of a connector. Therefore, the main goal is to execute the functional test suite in as many different Mule runtime environments as possible.

Test Setup

There are a few things to consider before running the functional test suite:

  1. This file stores the connector credentials and authenticated user related information. It is mandatory to have this file within src/test/resources.

  2. This file stores the list of required external Jars or native libraries.

Both these files need to be stored within <connector-project>/src/test/resources for running the functional test suite.

Be careful of excluding these files when committing changes.

The files is only mandatory if external, or native, libraries are required, as explained here.

Required Test Configurations

The connector must be tested with all available Mule runtimes environments from the MinMuleVersion to the latest runtime (MinMuleVersion is a parameter specifying the minimum supported Mule runtime for a given connector).

  1. Mule Runtimes: If a connector does not require an Enterprise Mule Runtime (i.e. it is not Premium nor Select) it must use Mule Community Edition Runtimes, such as 3.5.0, 3.6.0 or 3.7.0. Otherwise, it must use Mule Enterprise Edition Runtimes, such as 3.5.3 or 3.6.2.

  2. Java Versions for Mule Runtimes: Every Mule runtime environment needs to be bound to a particular Java version, in order to comply with Multi-Mule functional testing, as follows: Mule runtimes 3.5.X must use Java 1.6, Mule runtimes 3.6.X must use Java 1.7 and Mule runtimes 3.7.X/3.8.X must use Java 1.7. This can be achieved by configuring the wrapper.conf file within the Mule runtime conf directory and setting accordingly.

4.5.2. Testing Using CTF

The Connector Testing Framework allows you to run test suites in a specific Mule runtime environment, as explained here.

Two extra test properties should be added when running a test suite from the command line:

  1. Deployment Profile: By using -Ddeploymentprofile=local, CTF will run the test suite in a remote Mule runtime environment.

  2. Mule Directory: By using -Dmuledirectory:<mule-directory>, CTF will use the available mule runtime to run a test suite if -Ddeploymentprofile=local is used.

Using a simple Maven command from the connector’s root folder, and with Devkit 3.8.0 enabled you can perform tests on the connector in the runtime specified in your local profile, embedded runtime or an available CloudHub runtime version.

The fact that libraries change on CloudHub increases the potential for incompatibility between the Mule runtime version and your DevKit-based connector.
Deployment Profile Configuration

Pass the desired connector application deployment details as arguments to a single Maven command, specifying the environments you want to test your connector in. All arguments should be in lowercase.

If you do not specify -Ddeploymentprofile, the CTF runs by default in embedded mode.

Embedded Mode

Specifying only mvn clean test would run the functional tests in embedded mode, depending on the DevKit version. You are not required to have a Mule server to run the application in this mode.

Running mvn clean test is the same as running:

mvn clean test -Ddeploymentprofile=embedded
Local Mode

Running CTF in Local mode means loading the Mule application deployment specification from your user profile and running the test remotely. To test a connector using your local profile’s runtime, the argument -Ddeploymentprofile must be set in the /local folder. For example, the command would be structured like:

mvn clean test -Ddeploymentprofile= -Dmuledirectory=/local/usr/mule_3.6.3
CloudHub Mode

As of DevKit 3.8.0, CTF support for a CloudHub deployment profile is available, allowing you to test your connector in a more dynamic environment, a clear advantage to deploying a Mule application in a classic standalone environment. The two required parameters, besides specifying -Ddeploymentprofile=cloudhub, are your CloudHub username -Dcloudhubuser= and -Dcloudhubpassword=.

mvn clean test -Ddeploymentprofile=cloudhub -Dcloudhubuser=<your_username> -Dcloudhubpassword=<your_password>

4.5.3. Optional Parameters

When testing on CloudHub, you may specify the Mule version to run connector tests on, as well as the CloudHub URL and the CloudHub worker type for your instance. See the example below that includes all the required and optional parameters:

Optional Parameters Description


Configure the Mule runtime to be used on CloudHub


Gives the capability of change the CloudHub instance, by default the CTF deploys to


Allows you to configure the desired amount of vCores for the Mule application to be generated. The available options are: micro (0.1vCores), small (0.2vCores), medium (1vCore), large (2vCores), xlarge (4vCores)


Allows you to configure the timeout of the CloudHub instance where the Mule application is deployed

Example CTF test command:

mvn clean test -Ddeploymentprofile=cloudhub -Dcloudhubuser=<your_username> -Dcloudhubpassword=<your_password>

5. Anypoint™ Studio Interoperability Testing

Based on these guidelines, analyze the connector you’re testing and focus on processors that exercise the most representative cases


  • Flow contains a connector-dataweave-connector building block arrangement on the canvas.



Expected result


Configure both connectors with an operation returning and/or having an attribute of type POJO / List<POJO>, Map<String,POJO>, or List<Map<String, Object>>.

Metadata is fetched for both configurations.


On the DataWeave element click "Scaffold output structure" and accept.

"Select fields to scaffold" dialog type matches the Input Metadata of the processor (attribute annotated with @Default("#[payload]"))


Select all and click Ok

Scaffolding for the Input Metadata is written out automatically, Transformation and Output section reflect the changes


Click on the Structure tab of the Output section

Input Metadata of the processor is reflected


In the Input section select the payload and click on Sample data

Additional Payload tab is displayed that shows a sample input with placeholders for its fields.


Click on Regenerate sample data and accept.

"Select fields to use in sample data generation" dialog type matches the Output Metadata of the processor


Select all fields and accept

payload tab content is updated

6. CloudHub Interoperability

These items apply exclusively for connectors supporting OAuth authentication.

CloudHub’s Object Store is stateless (behaves like a proxy). This behavior is different from an Object Store in a local Mule application. For this reason, a simple application using OAuth must be run on the CloudHub platform to verify its correct behavior.

First, check that the callback URL on the application redirects to the URL set on the config­ref.

Make sure the domain on the Deploy to CloudHub dialog matches the one set for the callback URL.


qa guidelines cloudhub 1
<facebook:config-with-oauth name="Facebook" doc:name="Facebook"
consumerKey="206589772847469" consumerSecret="14b75847e7c9cca4159b3314b39fcd43">
    <facebook:oauth-callback-config domain=""
    localPort="${http.port}" path="callback"/>

Also make sure that the Mule version is the one under test.

Facebook Example

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns:json=""
       xmlns:spring="" version="EE-3.5.0"

    <facebook:config-with-oauth name="Facebook" doc:name="Facebook" consumerKey="${facebook.consumerKey}" consumerSecret="${facebook.consumerSecret}">
        <facebook:oauth-callback-config domain="" localPort="${http.port}" path="callback"/>

    <flow name="3.5.0-facebook-oauthFlow1" doc:name="3.5.0-facebook-oauthFlow1">
        <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="${http.port}" doc:name="HTTP" path="authFacebook" />
        <facebook:authorize config-ref="Facebook" doc:name="Facebook"/>
        <facebook:get-user config-ref="Facebook" doc:name="Facebook" user="hernan.wittemoller"/>
        <json:object-to-json-transformer doc:name="Object to JSON"/>

Note: remotePort should not be part of the config, and that the ${http.port} placeholder is to be used for ports.

Salesforce Example

  1. Generate keystore.jks running this command: keytool -genkey -alias mule -keyalg RSA -keystore keystore.jks

  2. Place keystore.jks it in src/resources.

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns:https=""
xmlns:sfdc="" xmlns=""
       xmlns:spring="" version="EE-3.5.0"
<sfdc:config-with-oauth name="Salesforce__OAuth_"
consumerSecret="${salesforce.consumerSecret}" doc:name="Salesforce (OAuth)" >
        <sfdc:oauth-callback-config domain="" localPort="${https.port}" path="oauthcallback" connector-ref="https_connector"/>
    <https:connector name="https_connector" cookieSpec="netscape" validateConnections="true" sendBufferSize="0" receiveBufferSize="0" receiveBacklog="0" clientSoTimeout="10000" serverSoTimeout="10000" socketSoLinger="0" doc:name="HTTP-HTTPS">
        <https:tls-key-store path="keystore.jks" keyPassword="password" storePassword="password"/>
    <flow name="3.5.0-everest-oauth-salesforce-twoFlow1" doc:name="3.5.0-everest-oauth-salesforce-twoFlow1">
        <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="${http.port}" doc:name="HTTP" path="oauth"/>
        <sfdc:authorize config-ref="Salesforce__OAuth_" display="POPUP" doc:name="Salesforce"/>
        <sfdc:get-user-info config-ref="Salesforce__OAuth_" doc:name="Salesforce"/>
        <logger message="#[payload]" level="INFO" doc:name="Logger"/>
        <set-payload value="Done" doc:name="Set Payload"/>

7. Documentation & Release Notes

Documentation is a vital part of the development stage. Your development team must strictly follow Mulesoft documentation standards described in this document.

7.1. Built-in Documentation

Part of the documentation must be packaged within the connector source code. The mandatory files are:

  1. User Guide

  2. Release Notes


In addition, create a folder named _images for image resources used in the documentation, one called attachments_ for user-downloadable content such as a JSON file or WSDL XML file, and one called sources_ for management of any code samples presented in the connector documentation, especially those which have associated Mule flow screenshots. It is important to give the corresponding image and Mule XML code the same name. The only thing that should differ are the file extensions, for example, connector-flow`.img` and connector-flow`.xml`.

7.2. User Guide

The user guide needs to be fully descriptive and easy to read, including not only technical documentation but use cases and error solutions. Write the documentation using AsciiDoc syntax so that the resulting file is called user-manual.adoc. Closely follow the template found here. It should reside in doc folder in the root of the connector project.

7.3. Release Notes

Release notes need to be highly descriptive, including backward compatibility of the released connector with previous versions. Closely follow the template found here. It should reside in doc folder in the root of the connector project.


A template can be found here. It should reside in the root of the connector project.

7.5. Connector APIdoc

Each connector requires:

  1. A description that provides a clear and a complete explanation of its purpose.

  2. XML samples of connector Configs (connection configurations) and Processors (the code that backs connector operations)

  3. Attributes that affect connector method behavior must be documented in detail.

For further information, refer to:

8. Appendixes & Templates

8.1. Connector Project Directory Layout

8.2. Common Public Attribution License Version 1.0 (CPAL)

8.3. Functional Tests Automation: HowTo

8.4. Anypoint™ Studio Interoperability Testing: HowTo

8.5. Anypoint™ Connectors Manual Test Suite Template