We’re happy to announce the 1.0 release candidate of MUnit – the unit and functional test framework for Mule. This is our first official release of MUnit and incorporates major usability improvements, broader support for Mule components and many bug fixes.
MUnit has been flying in stealth mode for the past year or two, and we’re finally ready to declare it ready for a much broader audience. MUnit came directly out of our work in building and testing Mule applications internally at MuleSoft and working with our customers, and is a test framework for creating unit and integration tests for Mule.
With MUnit you can easily create tests within Anypoint Studio. It is also fully integrated with Maven and Surefire for extensibility into your continuous integration environment. Within an MUnit test suite, developers have access to a full suite of testing tools
- Assertions for Mule messages to ensure the Mule message is what you expect
- Mocking of components inside a Mule flow (the service doesn’t need to be running in production)
- Verify calls and test the # of times an MP has been called: exactly one, at least #, at most #
- Spy on an MP before/after execution: Inspect the Mule message before/after calling a MP
- Set up and tear down sections for test suites
- Custom Assertions: extend framework as you see fit (e.g. complex validation)
If you’ve been using one of the beta releases, this release includes many new usability improvements and bug fixes, including:
- Create test suites from RAML files for APIkit testing
- Improved syntax for MUnit components
- Improved wizard for creating tests
- Support for testing Database and JMS components
- Support for specifying JVM arguments when launching tests
- Support for running a single test or group of tests using a file pattern
- And many bug fixes.