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.

On June 18th the London Chapter meets again for an evening of discussions, conversations, demos and stories. We have a very exciting evening planned for you with sessions from Ten10, Madhuri M...

Amy Phillips on what fifteen years in tech taught her about quality, ownership, and why removing things is just as important as building them.

Following the trend from Rosie and Dragan I tried the prompt too 😄The prompt: Hey ChatGPT, write a totally bonkers, unhinged bio about me (Parveen Khan) in 200 words.Then, create an image.

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.

A navigation UI pattern, typically three horizontal lines stacked in a corner, that expands to reveal a hidden menu when tapped or clicked. Common on mobile interfaces to conserve screen space. Named for its visual resemblance to a hamburger. A frequent subject of usability and accessibility testing.

An animated circular indicator shown in a UI when the system is processing a request or fetching data. Signals to the user that something is happening. A visible symptom of slow performance, and a common target for testing perceived responsiveness and timeout behaviour.

A small square UI element that a user can tick or untick to select or deselect an option. One of the most fundamental interactive controls in software interfaces, and a common focus for accessibility and state testing.

Informal term for the burst of version control conflicts that accumulate over a weekend when multiple developers have been working in parallel branches. A cultural shorthand in software teams for the workflow friction caused by divergent work and deferred integration.

A phrase used (sometimes defensively, sometimes genuinely) when unexpected software behaviour is reframed as intentional design. In testing culture it signals a gap between developer intent and user or tester expectation, and is a prompt to clarify acceptance criteria.

A phrase used when software behaves correctly in a developer's local environment but fails in another environment such as testing or production. A shorthand for environment inconsistency problems and a common source of tester-developer tension.