Architecting and deploying API implementations11% of the exam
MUnit Test Scope and Isolation
Set MUnit boundaries for isolated flow tests and real integration checks, with explicit source lifetime, mocking prerequisites and validation evidence.
Compare unit and integration tests and specify where MUnit is best employed.
~7 min read · 9 practice questions
What the exam expects
- Choose an isolated flow test or a test crossing a real integration boundary.
- Configure source activation and respect its test lifetime.
- Distinguish mock responses, event observation and invocation verification.
- Resolve initialization, domain and parameterized-suite prerequisites.
A suite contains MUnit tests; a mock replaces a processor call; a Spy observes execution; Verify Call checks invocation counts. These controls provide different evidence rather than interchangeable ways to make a test pass (test structure, Mock When, Spy, Verify).
Key facts
Real listener test
- Detail
- Enable its source and call it during Execution.
Initialization
- Detail
- Mocking does not remove connector startup prerequisites.
Unsupported targets
- Detail
- Logger and Transform Message cannot be mocked directly.
Dynamic responses
- Detail
- Then Call invokes helper-flow logic.
Spy
- Detail
- Event changes inside it do not persist outside it.
- Source
- Spy (opens in a new tab)
Counts
- Detail
- Verify Call works without a mock.
Error scope
- Detail
- Out-of-scope mocked types become
MULE:UNKNOWN.
Domain preflight
- Detail
- Workspace, naming and Maven dependency resolution all matter.
Data matrix
- Detail
- Parameterizations reuse test bodies with different values.
Suite version
- Detail
minMuleVersionestablishes a floor.
Sources for this section (7)
- Sourcesdocs.mulesoft.com (opens in a new tab)
- Mockdocs.mulesoft.com (opens in a new tab)
- Spydocs.mulesoft.com (opens in a new tab)
- Verifydocs.mulesoft.com (opens in a new tab)
- Domainsdocs.mulesoft.com (opens in a new tab)
- Parametersdocs.mulesoft.com (opens in a new tab)
- Structuredocs.mulesoft.com (opens in a new tab)
- When deliberately excluding an entire suite, where does
ignore="true"belong? - Why does an inline parameterization win when its key also exists in the suite's YAML parameterization file?
- When using
expectedErrorDescription, which relationship between actual and expected text is accepted?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 47 lessons of the MuleSoft Platform Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both