A small over a year ago, my team was confront a job. Without an machine-driven fixation and our team size reduced, how could we get sure that we had a good liberation? Although we certainly did testing within our teams, we just didn ’ t have the manpower to thoroughly check. We started using an untapped imagination in our testing — one that I had not heard about before. The conception was not new to the industry, but it was new to us. And it was efficacious. So what was our new witching resource? A bug bash!

Exploratory Testing On Steroids

The bug bash brings not but your tester to the table, but also people that may not feature any testing background - developers, labor managers, product possessor, support… the list could go on. Put aside your day-to-day, ho-hum task, and use your ware! Depending on the project, we would open the flesh up to several group — not just to our project teams, but also to people that work with clients day in and day out, who could give us a new perspective that perhaps we had not considered. If you work in a world where you have very little automation, a bug bash countenance you to expand what can be tested by others, and it ’ s a flying way to add resources (where we are constantly being asked to do more with less). Conversely, if you have all mechanization, this allows you to get human eyes on the ware. We found that our bug bashes gave us fresh eyes on the system. Whether citizenry work on one feature team and tested another country, or get from outside the department to help and saw the product for the 1st clip, we found that tired eyes missed thing, and tonic eyes found them. This lead to consistency across our product, and got us out of the mundane. The bad benefit of all, in my persuasion, was how much we found. Yes, it was a small scary, but we found bugs before guest did! Overall, we found a tincture under 20 % of the overall bug for our release. I ’ d wager to say this was more than what our automated regression used to find heading into a release. (Did I mention it was effective?)

A few lessons memorize ...

Of course, as useful as it is, we ’ ve had a few singultus along the way, and are adjusting where we can. I just wanted to portion a few things, should you opt to go down this path:

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

• Keep it Bracing!USE THIS TOOL WISELY. It ’ s a powerful weapon against bugs, but it can very easily be over-used, and then you lose the effectiveness. Initially we had a bug bash hither and there. The less often we had it, the more engagement we had. Then, we went hebdomadally. (Don ’ t do this.) The thought was to test as we render work in the sprint. Well, there is such a thing as too much of a full thing. I LOVE try, and I was combust out from it. Avoid bug bash burnout.

• Keep it fun!Gamify it! In the beginning, we had prizes! Best bug, most critical bug, most number of bugs found… We really had a competition on our hands. It worked. You don ’ t hold to drop money to get people to compete, but try to find a way to make people need to account just one more bug, plunk a small deeper, and stick involved. Some citizenry work on pride alone — get a live splasher up, show live results as bug come in!

• Keep it focus!We too had better participation (and results) when we would centre the bug bashes on particular area. Places we knew be weak and needed deeper testing, or whatever was new for the sprint. The more broad the search, the more lost your testers are travel to be. Have some charters, some general guidance, and let people loose. We besides had sign-up pages so people could pick from a list of features we wanted tested, and they could see where others were test.

• Keep it Social!We had grouping chats available during each session, and ensured Subject Matter Experts were answering questions from people who were not conversant with the features under test. Honestly this plausibly made the biggest difference in keep duplicates or no-fix issues because someone didn ’ t translate how things should work. It was also eye-opening to those of us that may hold been staring at a lineament for a few months and, while leisurely to us, it was maybe not so easygoing and intuitive to others. (And isn ’ t usableness important?) Yes, duplicates experience happened (a lot, even with the chat rooms), but if you have person who is not in QA testing, to be honest, they probably aren ’ t going to follow all of your better practices to a T. Just try to mitigate it.

Bash Away

Try it! I incessantly seek to improve, and even now, over a year after, we are even tweaking our procedure as we move to Uninterrupted Delivery and work to find the correct cadency, but we are getting there! Have you had successful bug bashes? I ’ d love to see about them (and the horror stories too). We can all acquire from each former!