Swap your team’s favourite quality superstitions, laugh at cursed demos and disappearing bugs, and turn “don’t deploy on Fridays” from folklore into smarter release habits.

I had a personal message thanking me for the gap analysis. The person had thought they were not good enough to apply for a role titled 'Quality Engineer'. But after taking the gap analysis, they fo...

I answered Simon's call for insights and had a great conversation with him all about my goals for 2026, and how I want to make thinking in testing visible, intentional, and teachable. I'm looking f...

I'm super excited to anounce our 2026 Ambassadors!! Make sure to follow them on the MoTaverse. And the 2026 Ambassadors of the MoTaverse are........... - Ady Stokes - Ben Dowen - Cassandr...

Meet Percy. We are looking after him for the day.

Reconnect with the MoTaverse through chapters, celebrate what’s changed while Deanna was away, and learn how local events help you grow your network and your craft.

All thing MoT in Leeds

Victoria Chan lead a workshop on embracing self promotion called I am remarkable. It was great to see everyone joining in and sharing their thoughts. Lots of ways to relate to the tech world. I’ll ...

Happy to be going to Leeds for the Chapter meeting, but the weather is terrible.

If 404 is not found, is 1404 mostly not found?

A variable is a named place in software where a value can be a range, rather than a fixed value. It represents something that can vary over time or between situations, such as a user’s input, a system state, a configuration setting, or the result of a calculation. Unlike constants, variables exist specifically to model change, uncertainty, and choice within a system. In software development, variables are fundamental to how logic is expressed. They let software respond to different conditions, handle multiple scenarios, and avoid hard-coded assumptions. In testing and Quality Engineering, variables are often where the most interesting risks hide. A variable can hold an unexpected value, something that can be updated in the wrong order, or be shared when it shouldn’t be. Even something that can move out of sync. Many bugs aren't caused by complex algorithms but by simple misunderstandings about what a variable can contain, when it changes, or who controls it. Variables are powerful test design levers. By deliberately varying inputs, states, and conditions, testers can explore boundaries, uncover hidden assumptions, and observe how the system behaves under change. Thinking in terms of variables encourages techniques like equivalence partitioning and boundary value analysis, etc. Examples of test cases using variables as inputs could be applying different discount percentages. Or a set of boundary values. Seen this way, variables are not just programming constructs. They represent where behaviour can change, where assumptions can break, and where good testing can provide the most value.