A vertical slice is a thin, end‑to‑end piece of a product that delivers a small but fully working part of a feature. It spans every layer of the system — from the user interface, through the business logic, down to the data or service layer. Unlike a horizontal slice, which focuses on one layer at a time, a vertical slice shows how all parts of the system work together to support a real user action. Vertical slices are valuable in testing because they expose integration points early, reveal risks sooner, and allow testers to evaluate real behaviour rather than assumptions or isolated components. They support fast feedback, help teams understand the true complexity of a feature, and make it easier to validate user workflows in realistic conditions.ReleaseA release is the process of making a specific version of a product or system available for use. It includes preparing, packaging, and delivering changes such as new features, bug fixes, configuration updates, or performance improvements. A release may be deployed to different environments — for example, test, staging, or production — depending on the organisation’s workflow.Releases are important in testing because they define what needs to be validated, when testing activities occur, and which version of the software is being evaluated. Testers often support release activities by verifying that changes behave as expected, checking that risks are understood, and confirming that the release is ready for users or customers. A release can be part of a planned schedule or delivered continuously in teams practising DevOps or continuous delivery.BuildA build is a compiled and packaged version of software created from the source code. It represents a specific snapshot of the product at a point in time and is generated by a build process or build pipeline. Builds are used for development, testing, and release activities, and they allow teams to verify that recent changes integrate and function as expected.Builds are typically identified by build version names, which are unique identifiers assigned automatically each time the software is built. Build versions help teams track changes, reproduce issues, compare versions, and understand exactly which code and configuration were included in a given build. They may follow simple incremental versioning (e.g., Build 1427) or more structured formats that include timestamps, branch names, or semantic versioning components.

Celebrate surprise-smooth demos, learn how solo testers spark better quality conversations, and explore “assumption investigating” as a core skill for making work clearer and kinder.

Loved having a chat with Jesse. We talked about our work and he gave me a very powerful story about his role and the work he did to be present in understanding the product and how its used, rather ...

Chris and Eamon kicking things off at Ramen Space for the second MoT London Chapter event.

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...

We wrapped up our first year of Ambassadoring, reflected on it, explored some ideas on how we can improve it. As time came to the end, I was saying thank you and wasn't sure how to say goodbye,...

Found a quiet moment between projects to break out the TestSphere deck. It’s a great way to step back from the "how" of testing and remember the "why." Looking at cards like Interruption and Requir...

What happens when you have 99 seconds to look at someone's MoT profile?