What is Mob Testing?

Mob testing is a collaborative practice where a whole group, often the entire team, tests the same feature together at one shared screen at the same time, combining many perspectives to explore deeply, share knowledge, and align quickly.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

Mob testing scales up pair testing to a group. Everyone focuses on the same feature on one screen: typically one person drives (operates the keyboard) while the rest navigate, suggest ideas, spot issues, and ask questions, with the driver role rotating regularly. The constant flow of diverse perspectives, developers, testers, product, designers, produces rich exploration and surfaces issues and assumptions no single person would catch.

Its strengths are deep collective insight, fast and broad knowledge sharing (everyone learns the feature and each other's techniques at once), immediate alignment on what quality means, and quick consensus on whether something is a bug. It is especially valuable for high-risk or complex features, for onboarding, for breaking down silos, and for building shared ownership of quality.

The obvious cost is that it uses the whole group's time on one task, so mob testing is used selectively, for high-value features, kickoff of a testing effort, or learning, rather than as a daily default. It differs from pair testing (two people) mainly in scale and from a bug bash (many people testing in parallel, separately) in that the mob works together on the same thing at once rather than dividing up.

WHY IT MATTERS

Why interviewers ask about this.

Mob testing appears in interviews about collaborative and team-quality practices. Explaining how a whole group testing together produces deep insight and shared ownership, while acknowledging the time cost (use it selectively), shows you understand modern, collective approaches to quality, not just solo execution.

EXAMPLE

Example scenario.

For a complex new permissions feature, the team runs a mob testing session: the whole squad gathers around one screen, rotating the driver, and within an hour their combined perspectives uncover several edge cases and a security gap, while every team member walks away understanding the feature and aligned on its quality bar.

TIP

Interview tip.

Define mob testing as a whole group testing the same feature together at one screen (driver rotates), scaling up pair testing. Highlight its strengths, deep exploration, knowledge sharing, shared ownership, and the cost (the whole group's time), so it is used selectively. Distinguish it from a bug bash (parallel, separate testing).

FAQ

Frequently asked questions.

What is the difference between mob testing and a bug bash?

In mob testing, the whole group works together on the same feature at one screen at the same time, sharing perspectives in real time. In a bug bash, many people test in parallel but separately, each exploring on their own to maximize coverage in a time-box. Mob is collective and focused; a bug bash is distributed and broad.

When should you use mob testing?

For high-value or complex features, kicking off a testing effort, onboarding, breaking down silos, and building shared ownership of quality, situations where deep collective insight and alignment are worth the whole group's time. Because it is resource-intensive, it is used selectively rather than as a daily default.