Requesting all to share your opinions and feedback on the following questions. These responses are to be used for automating the bug bash process.

1. Why do you use Bug Bash? Do you think Bug bash as a whole is efficient?
2. What is your role at a bug bash?
3. Please describe the steps in the bug bash for your team in a whole.
4. What are your pain points when you engage in a bug bash?
5. Which part in the bug bash is very smooth for you?
6. Can you find any place where it lacks from someone else's viewpoints?

PS: For your convenience, you need not respond to all the questions
Thank you.

April 9th, 2019, 05:36 AM

sanchay_2107

Automating the Bug Bash process

I'm working on the development to automate the bug bash process. Require your comments on the following things

1. Issues faced in the process of bug bash
2. Any feature of bug bash to automate

April 10th, 2019, 06:13 AM

Arjay

Re: [RESOLVED] Survey on Bug Bash

In my opinion the idea that a bug bash is necessary to find bugs points out a flaw in test coverage or test methodology. The rationale being if test cases are written which provide adequate test coverage and these test cases are executed (through manual or automated test means), there shouldn't be much else left for an ad-hoc bug bash to find.

Hello Arjay, Thanks for your response.
Well, I agree with the fact that manual bashing the development makes more sense. Otherwise it would steal the essence of bug bash. Automation word used here is with respect to improving the UX of the users who would be participating in the bug bash. This could be in terms of logging a bug, triage etc.The testing process would rather remain the same.
Thanks