15. Why MUnit?
What is MUnit?
• MUnit is a tool to implement test-driven development via the creation of unit tests
• Unit tests are discreet tests of a single unit of functionality.
• For the MuleSoft developer, this often boils down to a well defined Flow or Subflow
Why is MUnit Important?
• MUnit enables developers to rigorously and consistently test their code
17. TESTING EXTERNAL DATAWEAVE
• A DWL file with DataWeave fragments, which you can reference throughout your codebase
• https://docs.mulesoft.com/mule-runtime/latest/dataweave-create-module
What is External Dataweave?
• Good way to encapsulate complex transformation logic
• Did someone say, “Reusable”?
Why Use Them?
What does external
DataWeave have to
offer?
• Demo
And How Can I Test this?
19. Data Comes In Transform that Data Data Goes Out
What are a few strategies to pragmatically
test a transform component?
EXTERNAL TEST DATA
Input Transform Output
21. Often, a quality test is within reach using
very few testing tools
SIMPLE PROCESS
You are not confined to one way of
creating and shaping a test
BROAD TOOLKIT SATISFACTION
WHY MUNIT?
Does the code work as expected?
Will the code fail gracefully?
22. The WHY
Personal MUnit Hypothesis
Use MUnit because, as a MuleSoft developer, it's the tool I have to do
test-driven development, in order to deliver systematically rigorous
code.