This document provides an overview of MUnit and how to use it for testing Mule applications. It describes how MUnit allows creating tests using Mule code, mocking and spying on processors, making assertions, and generating test coverage reports. It also demonstrates how to use the MUnit database server and FTP server utilities to test code interacting with databases and FTP servers locally without requiring external dependencies. The document concludes with demonstrations of using MUnit to mock a processor response and test database interactions.

1. All contents © MuleSoft Inc.

2. All contents © MuleSoft Inc.

3. All contents © MuleSoft Inc.
MuleSoft Community…
https://www.mulesoft.com/community
 MeetUps https://meetups.mulesoft.com/
 Connect https://connect.mulesoft.com/
 Documentation https://docs.mulesoft.com/general/
 Help Center https://help.mulesoft.com/s/
 Developer Site https://developer.mulesoft.com/
MuleSoft Community Links

4. All contents © MuleSoft Inc.

5. All contents © MuleSoft Inc.
MUnit is…
• Integrated with Anypoint Studio, allowing you to create, design and run MUnit
tests just like you would Mule applications.
• It provides a full suite of integration and unit test capabilities.
• Integrated with Maven and Surefire for integration with your continuous
deployment environment
What is Munit?

6. All contents © MuleSoft Inc.
Overview of MUnit
6
With MUnit you can:
• Create your test by writing Mule code
• Minimize manual testing
• Mock processors
• Spy any processor
• Verify processor calls
• Enable or ignore particular tests
• Check visual coverage in Studio
• Generate coverage reports

7. All contents © MuleSoft Inc.
MUnit Suite Sub Modules
7
• MUnit
MUnit is divided in two main sub modules:
• MUnit Tools

8. All contents © MuleSoft Inc.
MUnit Operations
MUnit Module
8
• Before Suite - runs BEFORE executing MUnit Test Suite
• Before Test - runs BEFORE executing MUnit Test
• After Test - runs AFTER executing MUnit Test
• After Suite - runs AFTER executing MUnit Test Suite
– Examples of use
• To alter and/or clear an Object Store
• Create/Initialize/Delete a Test Database or FTP Server
• Test – adds a new test
• Set Event – sets a mule event
• Set null payload – defines a null payload for testing

9. All contents © MuleSoft Inc.
MUnit Tools Operations
MUnit Tools Module
9
• Assert - validate the state of a Mule event’s content
– Equals
– Expression
– That
• Mock when - mock an event processor when it matches the
defined name and attributes
• Spy - what happens before/after an event processor is called
• Verify call - verify if a processor was called
• Fail - allows you to fail your test on purpose
• Run custom - custom assertion

10. All contents © MuleSoft Inc.
MUnit Database Server
MUnit Utils :: Database Server
10
To test code that connects with a database
server, you must install a database server in
your local environment to run the tests.
• Option 1: Have a dedicated external database
server for testing:
– Maven project would not be portable
– 3rd party would need to install the testing
database server to compile your project
• Option 2: Use MUnit to implement a database
server in your local environment
• Define the structure and content of your
database:
– SQL
– CSV

11. All contents © MuleSoft Inc.
MUnit Database Server
MUnit Utils :: Database Server
11
• allows you to execute instructions on the in-
memory databases
• add or remove registries before a test
• check if your data was stored correctly
PROCESSORS
• Execute - operation to insert new values to the
table
• Execute query- operation to retrieve all values
from the table (including the newly added ones)
• Validate that – validates results of a query

12. All contents © MuleSoft Inc.
MUnit FTP Server Operations
MUnit Utils :: FTP Server
12
• To test code that connects with an FTP server,
you must install an FTP server in your local
environment to run the tests.
• Option 1: Have a dedicated external FTP
server for testing:
– Maven project would not be portable
– 3rd party would need to install the testing FTP
server to compile your project
• Option 2: Use MUnit to implement a FTP
server in your local environment

13. All contents © MuleSoft Inc.
MUnit FTP Server Processors
MUnit Utils :: FTP Server
13
• Contains files
– attempts to validate the existence of a file in the
FTP server
– if file is not present, the processor fails causing the
test to fail
• Remove
– instructs the FTP server to remove a file from
storage
– This feature is of use when we are creating the
same file name several times.
• Example, we can make use of it in an after-test to
ensure that no name collisions cause the test to fail

14. All contents © MuleSoft Inc.
Create an MUnit Suite
14
Various ways to create MUnit Tests
Method 1: File>New>MUnit Test Method 2 – Pallet Test Operation

15. All contents © MuleSoft Inc.
Adding Tests Creates XML
15
Various ways to add MUnit Test RESULTS: XML Creation
Method 3- From Flow

16. All contents © MuleSoft Inc.
• Behavior Scope
– Meant to set all the preconditions before executing the test logic
– Mocks and spies go in this section
• Execution Scope
– Meant to have the testing logic which will wait for all processes
to finish before executing the next scope
– Run flows in this section
• Validation Scope
– Meant to have all the validations regarding the result of the
execution scope
– Assertions and verifications go here
MUnit Test Scopes
16

17. All contents © MuleSoft Inc.
Set Event
Set Event Processor
17
– Allows you to define a Mule Event.
– Normally used at the beginning of an
MUnit test, to define the first message
to send to the flow being tested.
– You can define as many properties per
each scope as you need for your test.

18. All contents © MuleSoft Inc.
Assert that
Assert That Event Processor
18
– Allows you to run assertions to validate the state
of an event’s content
– Can validate the event after the production code
runs
– Uses DataWeave functions called MUnit matchers
to define the assertion conditions for any value
in an expression
– Include the prefix MunitTool:: in the expression
• notNullValue() checks that the expression is not null.
As shown: #[MunitTools::notNullValue()]

19. All contents © MuleSoft Inc.
Matchers
Assert That MUnit Matchers
19
• Core Matchers - evaluate core values in
the expression
• String Matchers - perform assertions on
String expressions
• Comparable Matchers - compare the
expression against a specified value
• Iterable and Map Matchers - when your
expression is an array or a map of data
• withMediaType(String)
#[MunitTools::withMediaType('text/xml’)]
• containsString(String)
#[MunitTools::containsString('example’)]
• greaterThanOrEqualTo(Comparable)
#[MunitTools::greaterThanOrEqualTo(20)]
• isEmpty()
#[MunitTools::isEmpty()]
Examples

20. All contents © MuleSoft Inc.
Mock when
Mock When Event Processor
20
• Allows you to mock an event processor when it matches
the defined name and attributes
1) Pick processor
2) Select target processor
3) Select attributes
4) Click OK

21. All contents © MuleSoft Inc.
Configure “Then return” section
Mock When - Then Return
21
• Configure Then Return to define the type of
response the mocked processor should
return
• It could be a payload, a variable, attributes,
or even an error
1) Choose type of response
2) Click Add icon
3) Enter values
4) Click OK

22. All contents © MuleSoft Inc.
Spy
Spy Event Processor
22
– Allows you to spy what happens before and
after an event processor is called
– Tells MUnit to run a set of instructions before
and/or after the spied event
1) Pick processor
2) Select target processor
3) Select attributes
4) Click OK

23. All contents © MuleSoft Inc.
Verify Call
Verify Call Event Processor
23
– Allows you to verify if a processor was called
– you can validate if a specific processor has
been called:
• with a particular set of attributes
• a specific number of times

24. All contents © MuleSoft Inc.
Run MUnit Suite Select src/test/munit>Run As>Munit
Run MUnit Suite
24
• Right click Canvas
• Select Run MUnit suite

25. All contents © MuleSoft Inc.
Run MUnit Test
25
Run MUnit Test
• Right click In Test
• Select Run MUnit test

26. All contents © MuleSoft Inc.
DEMO #1 on MUnit Mock When - Then Return

27. All contents © MuleSoft Inc.
DEMO #1 Flow Details
27

28. All contents © MuleSoft Inc.
DEMO #1 MUnit Details
28

29. All contents © MuleSoft Inc.
DEMO #1 MUnit Test Results
29

30. All contents © MuleSoft Inc.
DEMO #1 MUnit Test Coverage Report
30

31. All contents © MuleSoft Inc.
DEMO #2 on MUnit Utils :: Database Server

32. All contents © MuleSoft Inc.
DEMO #2 MUnit Global Elements
32

33. All contents © MuleSoft Inc.
DEMO #2 Flow Details
33

34. All contents © MuleSoft Inc.
DEMO #2 MUnit Test Global Details
34

35. All contents © MuleSoft Inc.
DEMO #2 MUnit Test Coverage Report
35

36. All contents © MuleSoft Inc.
View test results and coverage
MUnit Coverage Report
36
1) All the tests for all test
suites
Green means successful
2) Errors: shows the
reason for test failure
3) Coverage: % of the
flow that were covered
4) Detailed coverage
report.

37. All contents © MuleSoft Inc.
Failures
Munit Failures
37
Munit Test Suite
FAIL
SUCCESS

38. Thank you