Avoiding the pitfalls of tightly coupled mocking

Are JUnit 5 nested tests here to save the world? Probably not.

Characteristics to aspire to when writing tests

They say that naming is one of the hardest problems in software engineering. Well, perhaps. It’s at least one of the most common hurdles we need to clear.

A quick tip to fix a mocking gotcha.

When it comes to shell scripting, although I’ve developed on UNIX-like systems for years and there’s even been times when my primary task was writing shell scripts, I seem to only ever retain a level of understanding that “gets the job done”.

Using RxLint to highlight RxJava Scheduler mistakes

The official plugin hooks to override Schedulers

Using the Provider pattern to easily override Schedulers