#9 Calicut MuleSoft Meetup - Munits in Mule 4.pptx
- 1. 03rd June 2023 Calicut MuleSoft Meetup Group #9 MUnit in Mule 4
- 2. Safe Harbour Statement â Both the speaker and the host are organizing this meet-up in individual capacity only. We are not representing our companies here. â This presentation is strictly for learning purposes only. Organizer/Presenter do not hold any responsibility that same solution will work for your business requirements. â This presentation is not meant for any promotional activities. 2
- 3. A recording of this meetup will be uploaded to events page within 24 hours. Questions can be submitted/asked at any time in the Chat/Questions & Answers Tab. Make it more Interactive!!! Give us feedback! Rate this meetup session by filling feedback form at the end of the day. We Love Feedbacks!!! Its Bread & Butter for Meetup. Housekeeping 3
- 4. Organizers Fathima Farzana NJC Labs MuleSoft / Integration Developer John Mathew Philip NJC Labs MuleSoft / Integration Developer Anoop Ramachandran NJC Labs Technical Instructor / Integration Architect
- 5. https://www.linkedin.com/feed/update/urn:li:activity:7069907733281406977/
- 6. â MuleSoft Ambassador â MuleSoft Meetup Speaker â Guwahati & Lucknow Meetup Leader â Certified MuleSoft Developer & Architect â Total 8 years of experience (6 in MuleSoft) â Working as Associate Solution Architect at Apisero Inc. Abhishek Bathwal Apisero Inc Associate Solution Architect â About the Speaker Introduction linkedin.com/in/abhishek-bathwal- 49360694 youtube.com/@abhishekbathwal1805 youtube.com/@developersguide5562 6
- 7. 7 Agenda Introduction To Munit Different Approach of Writing Munit Limitations of Test Recorder Munit Tools and Components Executing Munit Suits Munit Coverage Live Demonstration
- 9. 9 MUnit is Anypoint Platformâs dedicated unit testing tool specifically designed for Mule applications. It runs inside a Mule runtime, manually in Anypoint Studio, and automatically as part of the Maven-based CI/CD build process. MUnit is designed to create structural test cases as Mule flows. That means you can use components on top of MUnit and MUnit tool modules. What is Munit?
- 10. 10 Different Approach of Writing Munit â Munit Test Recorder â Manually
- 11. 11 Limitations with Test Recorder The test recorder is limited in the following ways when you create MUnit tests: â You cannot create tests for flows with Mule errors raised inside the flow or already existing in the incoming event, not even if they are handled by an on error continue error handler. â A recorded flow execution ends successfully, but the result does not reach its destination because the application is killed. â Your validations fail every time your test runs if you configure Spy or Assert processors to assert values for random data, time-dependent information (such as timestamps), or values resulting from parallel processes, because those values change in every execution. â Mocking values resulting from parallel processes causes a mixture of real and mocked data that compromises the execution of the processors that follow in your test. â Although the recorder supports data iteration in the flow, such as recursivity or loops, it does not support cases in which the structure of the data being tested changes inside the iteration. â The recorder does not support mocking a message before or inside a Foreach
- 12. 12 â Test â Mock When â Set Event â Asset That â Assert Equal â Asset Expression â Verify Call â Spy Munit Tools and Components
- 13. 13 Executing Munit Suite â From Studio â From cmd (mvn clean test)
- 14. 14 Munit Coverage The MUnit Coverage feature provides a measurement of how much of a Mule application has been executed by a set of MUnit tests by counting the amount of event processors executed.This allows you to obtain a quality standard for your application, and provides metrics for: â Application overall coverage: An average of the items below. â Resource coverage: Refers to each Mule configuration file under src/main/mule. â Flow coverage: Refers to any of the following components: Flows, Sub-flows, and Batch jobs.
- 15. 15 â <ignoreFlows> <ignoreFlow>FlowName</ignoreFlow> </ignoreFlows> â <ignoreFiles> <ignoreFile>FileNamet.xml</ignoreFile> </ignoreFiles> Ignoring Files or Flow
- 17. Batch Processing Mule batch processing components are designed for reliable, asynchronous processing of larger-than- memory data sets. The components are the Batch Job, Batch Step, and Batch Aggregator. The Batch Job component automatically splits source data and stores it into persistent queues, which makes it possible to process large data sets while providing reliability. In the event that the application is re- deployed or Mule crashes, the job execution is able to resume at the point it stopped. 17 Phases: â Load and Dispatch â Process â On Complete
- 19. Demo
- 20. 20 â https://docs.mulesoft.com/mule-runtime/3.6/munit â https://docs.mulesoft.com/munit/2.3/test-recorder â https://blogs.mulesoft.com/dev-guides/how-to-tutorials/munit-testing-strategies/ â https://dzone.com/articles/mock-apikitrouter-and-write-munit-test-cases-for-d â https://youtu.be/iLTqZ_ZcdEs â https://docs.mulesoft.com/mule-runtime/4.4/batch-processing-concept â https://javastreets.com/blog/2017/9/mule-batch-processing-part1-introduction.html â https://billennium.com/blog/munit-for-batch-module-in-mule-4/ Reference
- 21. Q&A
- 22. Take a stand ! 22 âNominate yourself for the next meetup speaker and suggest a topic as well.
- 23. 23 â Share: â Tweet using the hashtag #MuleSoftMeetups â Invite your network to join: https://meetups.mulesoft.com/calicut/ â Feedback: â Fill out the survey feedback and suggest topics for upcoming events â Contact MuleSoft at [email protected] for ways to improve the program Whatâs next?
- 24. Thank You