One of the most valuable characteristics of DataWeave is that it is a functional programming language. This means it is dynamically able to solve problems with various approaches — one being currying, which is a common feature of functional programming languages like Haskel (from where it derives), and JavaScript.
In this post, I’ll explain what currying is and how to write curried functions in DataWeave.
Unit tests are executed at different stages during the development life cycle. As mentioned in the first blog post of this series, MUnit for Java Programmers: Introduction, unit tests play an essential role in the implementation, maintenance, and evolutionary stages of a project’s life cycle. Tests can be executed during each of these stages and the results are collected and analyzed. Should the application pass the series of tests it will continue on its journey through the project’s lifecycle.
A test double is a term used to describe replacing a dependent component of the functionality that is being tested with a dummy version of the real component — similar to a stunt double, only for unit tests. The test double only needs to emulate the behavior of the original dependent component closely enough that the functionality being tested doesn’t detect it’s not using the real component.
Test fixtures, also known as a test context, sets up the conditions for a test to run. These test conditions will be a known good state that is specific to the code under test. When the test is completed, the state is restored or torn down. Conditions can be set up before a test suite executes and before a test runs. Test suites are extended further by parameterizing executions, enabling the same test to run different inputs.
At the heart of unit tests are assertions which provide a mechanism for comparing expected outcomes with actual outcomes. JUnit provides a large selection of overloaded convenience methods that perform predefined logical assertions, such as testing for equality, negations, and conditions specified by a matcher. MUnit also provides a similar set of assertion capabilities such as to assert two values as equals, validate a logical condition, and a variety of other custom assertions that replicate familiar JUnit assertions.
Unit tests are an integral part of the software development lifecycle. However, for most it is a task that must be endured and compounded by what seem like arbitrary test coverage targets.
In this blog, I will introduce MUnit by making reference to concepts already familiar to Java developers, thereby making the transition to MuleSoft developer and architect smoother.
There’s a revolution underway in enterprises, as businesses look to digitally transform to enhance the customer experience. From seamless omni-channel shopping to voice activated connected devices, customers expect businesses to evolve rapidly and deliver experiences they value. We are in the middle of one of the most important economic movements in a generation, often referred to as “uberization.” This is shifting businesses away from traditional models and towards an “everything-as-a-service (XaaS)” model that combines: instant gratification,
