JFairy VS Awaitility

In my observation, mock data has tended to be used in a rather loose, slipshod, careless manner. Unlike documentation, it is treated as the garbage of software material. (Sometimes even referred to as "garbage data"). People will try to avoid writing it by using elaborate "generators" such as jFairy or zed.

I’ve coded in Java since the first beta, even back then threads were at the top of my list of favorite features. Java was the first language to introduce thread support in the language itself, it was a controversial decision back then. In the past decade, every language raced to include async/await and even Java had some third-party support for that… But Java zigged instead of zagging and introduced the far superior virtual threads (project Loom). This post isn’t about that.

I hope everybody knows https://github.com/awaitility/awaitility by now.

And finally the tests, using Awaitility as we are testing asynchronous stuff:

awaitability: A tool to express expectations for asynchronous system in an easy and concise manner.

Awaitility with version 4.1.0 comes with fail fast feature (2m read) 🎉 https://github.com/awaitility/awaitility/wiki/Usage#fail-fast-conditions

Given our new functionality to update the membership list, we can create a new test case where two nodes join the cluster and expect that to be reflected in the local state of each node eventually. Thanks to the Awaitility DSL we can conveniently wait for the eventual update to happen.

Nota: para los que no la conozcáis, await es un operador de awaitility, muy útil para validación de resultados en procesos asíncronos.