On Test Automation

Earlier this year, I wrote a blog post about increasing focus in my career.

This post was previously published through my newsletter on May 25, 2026.

Just a quick update to let those of you who bookmarked this blog or who have subscribed to my RSS feed know that I have (re-)started a newsletter.

From what I’ve seen over the years, tests that exercise a system through the graphical user interface are disproportionally likely to fail for reasons other than an actual, genuine product failure.

When I talk about the goals and the purpose of test automation, I often use the phrase ‘valuable feedback, fast’: we use tools to support our testing to help us get valuable information about the state of our product in the most efficient manner possible.

Note: this is not the most well-structured blog post I’ve written, but rather a recording of my not (yet) completely organized thoughts.

In a recent post, I wrote about how I used Claude Code to analyze the code for RestAssured.Net and then perform a refactoring action, using handwritten tests as the safety net.

As some of you might know, the workshops and training courses I run, the talks I do and the blog posts I write tend to focus on fundamental sofware testing, software development and test automation skills, rather than focusing on the latest technology and…

About six weeks ago, I decided to take some time away from LinkedIn.

Earlier this week, I ran my first two training sessions of 2026.