MuleSoft | Read the latest blogs, news and views from Infomentum. (5)

Testing is a critical part of software development, ensuring early detection of bugs or any other problems within your code. However, for most of us it's the less favorite activity; it feels tedious and often repetitive. Furthermore, creating test for a large block of code can be troublesome, especially for beginners.

API-led integration can propel your organisation to new heights; better customer service, increased efficiency and innovation are only a few of the benefits of a successful initiative.

Unit testing has always been an integral part of software engineering because it ensures that problems in the code are isolated and fixed long before they become an issue in production. With the introduction and adoption of Agile framework, unit testing has changed dramatically because of the test-driven development (TDD) methodology. TDD is a software development strategy in which unit tests are used to drive the development process. In this blog, I explain how to practice TDD and share some tips on how to write great unit tests using MUnit.

Today, I want to explain how to use pom.xml to resolve APIs' common dependencies that might lead to duplication and mismatch in MuleSoft Mule4.

The pom.xml file contains the core information about a project and its configuration details, including its dependencies, build directory, source directory, test source directory, plugin, goals etc. Maven reads the pom.xml file and then executes the goal.

Notifications could be a very powerful tool to get visibility into business-related events inside your application.

MuleSoft has exposed an API that provides access to Anypoint MQ administrative functionality. For those who are not familiar with Anypoint MQ, it's a multi-tenant, cloud messaging service that enables customers to perform advanced asynchronous messaging scenarios between their applications. Using this API you can perform a series of actions that otherwise would only be accessible through the Anypoint Platform's web interface. And since many organisations prefer to externalise and automate this type of processes using scripts, I would like to explain how to use all four basic CRUD methods (Create, Read, Update and Delete) using this API.

Recently, one of our customers requested to consume RPC-style web services built on top of a legacy system. Unfortunately, I then discovered that RPC WSDL were not supported by the Web Service Consumer connector in Mule 4. Want to know the solution?

If you read my last blog post on May's MuleSoft Summit, you'll remember that I told you I got a sneak peek at MuleSoft's roadmap.

Well, that functionality has now been released.

On July 29th, MuleSoft's Crowd release went live. It seemed like a long wait, but it was finally time to put my hands on the new Anypoint Exchange 2.0 and the completely new component, Design Center. Now that I've had a few days to take a look around at all of the new functionality, I'm rounding up my highlights below. 

I'm an Integration Consultant and part of Infomentum's wider integration team. As well as being a MuleSoft trainer, I'm a certified MuleSoft developer and an Oracle SOA suite specialist.