Tech | Read the latest blogs, news and views from Infomentum. (6)

Are you in the middle of working out your integration strategy and selecting a suitable platform? It's a serious and long-term commitment, so wouldn't it be great to test a chosen platform first? Validate it by building fully-functioning API integrations for your specific use case?

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.

In my experience, when working with Interactive Grid, most of the times, we need to open a modal popup to interact with selected records (single or multi selection). For example, let say we have an Interactive Grid listing some records and you want a button which bulk updates all selected rows with the same value.

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.

While crime rates in the UK have dropped by more than 20%, cybercrime seems to be on the rise. Phishing related attacks are up by a staggering 667% compared to pre-pandemic February, and more than £2M has been reported lost by victims of Coronavirus-related scams. Despite common belief, not all cybercriminals are technology wizards who spend their days in a basement hacking into government servers. Some use simple tricks and social engineering, which hardly require technical expertise.

If you read my previous blog post on competing in the API economy, you probably have a feel for just how important APIs are for modern organisations. Implementing an API strategy unlocks internal assets and makes you a competitive and relevant force in our diverse and fast-changing tech landscape.

There is still much confusion about the differences and commonalities between SOA (service-oriented architecture), microservices, APIs and, even, point-to-point integration.

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.