An Introduction To Bug Bash Testing

Nowadays Bug Bash Testing is usually employed in the industry. It is basically the testing technique where all Testers, Developers, Designers and the complete team go through the product in different ways they can think of. The main idea behind this kind of testing is to find as many bugs as possible with different perspectives like exploratory testing, functional testing.

The idea of Bug Bash Testing involves the non-testing members of the team and use their skills to find bugs and gather product’s real-time feedback.

QA’s should have a certain kind of expertise skills so as to participate in the Bug Bash Testing. The basic skills can be testing knowledge, bug reporting, writing Test Plan Document, writing Test Cases. Apart these, some specific skills are needed to perform such bug bashes.

Following are the  major ways to do Bug Bash testing

1.Read – Observe – Perceive

Testers involved in the Bug Bash cycle should step by step read, understand, re-read if required the project and project’s requirements and expectations out of the test cycles. This very helps in finding useful and relevant bugs so that those bugs can be prevented from getting rejected afterward. Following this process can build a long-term relationship of trust and appreciation between client and the team. Therefore a Bug Bash tester must have

Understand requirements in detail

Patience needed in reading & understanding the requirements before going to testing.

Limit actions to the scope of test cycle

Curiosity and insight

2. Communication: Bugs are to be reported in a symmetric format since there is no direct communication sometimes with the developers. So testers must prefer those reports and should provide the proof to support the defect by taking screenshots, videos, crash reports etc. Also, the defect reports must be clear and there should be precise communication with the Lead, Clients and other Team members.   

Communicate till the requirements are not clear. Screenshots or recordings can be saved in different devices and Application logs, System logs should be attached wherever possible.

3. Exploratory Testing: Exploratory approach is much more needed while performing Bug Bash Testing as the tester performs learning and testing simultaneously. An organized approach should be followed to achieve the maximum out of time and effort spent on the project. Following techniques can be used for the same.

Test sessions based on a particular feature, typically for 1-2 hours can lead to proper learning and to find quality bugs.

A good practice is to use recording step by step performed during the test session which covers the whole session and can be used later for logging issues.

Keep a Test log- which is a brief record of areas covered, bugs found and questions or doubts- which can later be clarified with the test leads and fellow testers.

To keep a test log is must, which briefs you about the bugs found, area covered, queries or doubts, which can be clarified later on. Also, logs can be used for re-verification.