Theresa Neate is a career tester and test consultant who loves lean and agility and advocates for holistic system quality – and therefore all things DevOps. She has 2 decades of IT and non-IT testing and QA experience, coming recently from the ThoughtWorks consultancy stable, followed by a stint at Australia Post’s Digital Delivery Centre and is now working for digital media icon REA Group in Melbourne, Australia. REA are a global digital media company who want to change the way the world experiences property. Their leading brand is Australia’s largest online property audience, realestate.com.au.
You can find Theresa at https://twitter.com/TeresitaTheresa and at theresaneate.com.
Wikipedia defines a bug bash as: “… a procedure where all the developers, testers, program managers, usability researchers, designers, documentation folks, and even sometimes marketing people, put aside their regular day-to-day duties and ‘pound on the product’—that is, each exercises the product in every way they can think of.”
I first learned to do a bug bash after hearing the term about 8 years ago. I taught myself a crash course from a Google search, and then devised my own flavour of bug bash (which continues to evolve every time I run one).
The term “bug bash” seemingly first appears in Ron Patton’s book “Software Testing”1 (first published in 2001). As with many others, it does not surprise me that the term has been around for much longer than I have known it.
In this article I will describe why and how I run a bug bash these days – and hope you too find value in it, as I have since my Google searches years ago.Continue reading →