Bug bashes enhance collaboration, provide diverse perspectives on your product, and help build and reinforce quality culture. A bug bash usually looks something like this: You invite a cross-functional team: testers, developers, product owners, designers, stakeholders. Maybe it's just your product team, or perhaps you want to invite some folks who don't usually attend your team meetings, like legal or marketing. Make sure to invite some folks who haven't yet used the product (or haven't yet tried new features). You set out some guidelines for how to test the product. Just as at a social party, you need to be a good host, and setting out clear guidelines and expectations is part of that. Make it fun! Gamify testing (some tips below).  For a few hours or maybe even a few sessions of a couple of hours, the team focuses on testing the product, following the guidelines you laid out.  Make sure to include break times. Snacks and drinks are always welcome, too. 

Have a browse of our upcoming community-led meetups

Explore tips for organising an inclusive, creative, and collaborative bug hunting session that enhances product quality

An amazing panel full of brilliant insights

Join Simon Tomes and his team of global correspondents.

Learn from three huge leaders in the influencing space.

Panel Event - "Shifting Testing, Left or Right?"

Watch "A Tester’s Survival Guide for Agile Transition" with Parveen Khan from TestBash Germany 2019