Did you catch my two 99-second talks at UK 2023?

Want to identify and fill gaps in your system testing?

Great! Go sign up for my masterclass "Teamwork Makes the Full-Stack Testing, Dream Work",


FREE to attend live, recorded for Pro members.


We developers sometimes shrug off explaining a change of technical nature as architecture change, refactoring or rewrite. This bites us later when we are seemingly doing the same thing nth time even though it’s different. There is almost always a better label we can apply.

When do you discover if a bug has value?

Do you dismiss small bugs to focus on finding bigger issues, or log everything and figure it out later?



Over my career in Software Testing, I’ve had the pleasure to analyze and model a lot of systems.

Some of them have had tons of formal architecture models and others have had little more than a few epics and user stories held together by smart engineers and sticky tape.

One of the things I’ve found useful over that time is zooming in and zooming out.

Continue reading over on my blog:


I recently reviewed some testing from a Dev on my team, where they had initially made some measurements of production workload, and observed 11 requests per second. Then, they designed a test with 11 users, with a 1 user per second spawn rate, and unconstrained requests per second.

I’m keen to know, what do you fix when you’re doing performance testing? What do you leave unconstrained?


In my recent experience, I’ve found a few things that help set up a successful collaborative testing session.

Agree on a mission
Invite 2-5 people
Setup the software
Take notes
Share an adventure
Reflect on the experience


I want to hear, what is the most misunderstood part of your job?

To put it another way, what part of your job do you wish your colleagues, recruiters, and hiring managers would understand better?


What’s the longest time you’ve waited from raising a bug to it getting fixed?

For me, it was well over 5 years, and long after id left the company. Read more and join the conversation on the club!


5 ways testing mobile is different from web


Web runs on almost any device from a games console to a tricked out multi-core desktop PC with a huge high resolution screen.

... more when you read the full blog:


That shiny new feature works, so what?

In my latest blog post, I look at how the work of your team can be put into a wider context to better understand the quality and how your users actually get to experience it.


What makes up a software stack?

I like to think of a software stack, also referred to as a technology stack, as the different layers of technology that build on top of eachother in order to make a functioning system.


Some days it feels like it's all meetings, planning, tasks away from the "core" role.

I often like to ask myself, "what can I test today?", so I can do at least a bit of testing!

I know plenty of developers who also often moan they don't get enough time focusing on writing code.

What do you do to re-focus and allow yourself time to do the thing you want to do?

And yes, the other tasks can be useful, and important.

Show older
Software development is a social activity

A social place intended as a chill hangout place for software testers, developers, or just about anyone involved in delivering software and who is interested in both the technical as well as the social side of things.

sw-development-is.social is supported by the Association for Software Testing.

For more information about this instance,