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.
Release
A 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.
Build
A 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.
Release
A 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.
Build
A 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.
