Code that is easy to read, understand, and maintain by humans, not just machines. Clean code expresses its intent clearly through meaningful naming, small focused functions, and minimal complexity, so that any developer can work with it confidently without needing to decipher what it does.

A technique for assessing what parts of a product, requirement set, or feature area have been tested, used to showcase QA work and identify gaps that need attention.

Work that has accumulated and remains unaddressed from past projects, which teams have to prioritise against current work and capacity, often through a percentage allocation of team capacity.

Time-based exploratory testing sessions with structure around them, used as a way to demonstrate the value of exploratory testing as a complement to or alternative to documented test cases.

A collection of test cases run repeatedly to verify that previously working functionality still works after code changes. Often used as the evidence base when teams ask whether new test cases need to be written for past projects.

The idea that quality is built into the product as it is developed rather than checked at the end, requiring conversations across the team about what quality looks like before work begins.

An approach where quality is a shared responsibility across everyone on the team, not just testers, including developers, designers, product, and other disciplines collaborating on what quality means and how it gets built in.

A set of seven guiding principles created by the AB Testing podcast hosts, including the idea that only the customer or end user can judge the quality of a product. Used as an alternative framing to traditional testing principles.

A group of people inside an organisation who share an interest or discipline and meet regularly to share knowledge, watch talks together, discuss techniques, and learn from each other. Can extend beyond a single function to include developers, designers, product, customer services, and field operations.

An organisational structure used in software development where teams are arranged into squads, tribes, chapters, and guilds. A chapter, for example, brings together people with similar skills across squads, like QAs from different teams meeting as a QA chapter.

A small contextual label or description that appears when a user hovers over or focuses on a UI element. Tested for timing, accuracy of content, accessibility (screen reader compatibility), and whether it obscures other content.

A UI control that switches between two states, such as on and off, enabled and disabled. Visually resembles a physical light switch. Tested for correct state persistence, default values, and the accuracy of any downstream behaviour it triggers.