DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Handle HL7 MLLP Messages With Mule 4
  • MDC Logging With MuleSoft Runtime 4.4
  • MuleSoft Integration With RabbitMQ
  • MuleSoft APIkit Router - QueryParam and Header Strict Validation Configuration

Trending

  • Introduction to Error Prone: How to Catch Bugs at Compile Time
  • Implementing Idempotency in Distributed Spring Boot Applications Using MySQL
  • Idempotency Under Concurrency: Why Your Application Check Isn't the Last Line of Defense
  • How to Keep AI Agents From Going Rogue Using Docker Sandbox

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Data Engineering
  3. Databases
  4. MUnit Testing With Mulesoft: Part II (Mock Message Processor)

MUnit Testing With Mulesoft: Part II (Mock Message Processor)

The Mock component is useful in various scenarios of Mule application testing. In this part of the series, we will see how to use the Mock component in an MUnit test.

By 
Jitendra Bafna
·
May. 01, 17 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
26.3K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

This tutorial continues from Part 1.

Mock is a feature provided by MUnit to mock the behavior of the message processor. Basically, MUnit replaces the actual behavior of message processor with the behavior defined by us.

There are various scenarios where we can use the Mock Message processor. We have completed the development of your Mule application and need to test it, but in our application, there is a database connector in the message processor region and the database is not ready to accept any request; but, we still want to test the application. In such cases, we can mock the normal database connector behavior.

There can be more scenarios, like we are connecting to JMS queue but JMS is not ready, and we want to test the application. In such cases, we can again make use of mock message processor.

Let's walk through how to use the Mock component in MUnit test. Below is the flow for which we will create MUnit tests and will mock set-payload component.

Image titleRight click the flow and create the MUnit tests. It will create MUnit tests in the folder src/test/munit of your Mule application.Image title

Define the Message Processor to Mock

Drag and drop the Mock component in the setup region of MUnit test.

Image title

  <mock:when messageProcessor="mule:set-payload" doc:name="Mock">
            <mock:then-return payload="#['Sample Message']"/>
        </mock:when>

 messageProcessor  is used to specify the message processor to be mocked. In this case, we have mock set-payload component.

Define the Mock with Attributes

When we have more than one similar component (i.e. 2 set-payload) in our Mule flow but we want to mock only one set payload. In that case, we need to add attributes in the Mock component which accept name and value of message processor.

Below is the Mule flow having 2 set-payload and we need to mock only one component.

Image title

We can define attributes as shown below to mock one set-payload.

Image title

   <mock:when messageProcessor="mule:set-payload" doc:name="Mock">
            <mock:with-attributes>
                <mock:with-attribute name="doc:name" whereValue="setPayload1"/>
            </mock:with-attributes>
            <mock:then-return payload="#['Sample Message']"/>
        </mock:when>
  •  name  is the name of attribute and it cannot be MEL expressions.

  •  whereValue  is the value that the attribute of the real message processor should contain. It accepts MEL expressions.

Below is the video tutorial:


Now, you know how to mock the message processor with MUnit.

Testing application MuleSoft Attribute (computing) Flow (web browser) Database Connector (mathematics) Drops (app) Payload (computing) Requests

Opinions expressed by DZone contributors are their own.

Related

  • Handle HL7 MLLP Messages With Mule 4
  • MDC Logging With MuleSoft Runtime 4.4
  • MuleSoft Integration With RabbitMQ
  • MuleSoft APIkit Router - QueryParam and Header Strict Validation Configuration

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook