Bug Bash
Collaborative event where devs, QAs, POs, do exploratory testing to find bugs
Since all the stakeholders will see things from different perspectives, bug bash will be conducted
Have to find as many bugs as possible in a timeframe
After QA Testing
Bug cards will be created after the bug bash
Why Bug Bash
- Quality Release
- Diverse perspectives
- Discover large number of bugs in a short span of time
- Shared Responsibility
When Bug Bash
- Before major releases
- 1/2 weeks before going live
- Before Beta testing
- UAT Testing
- Bi-monthly / Monthly
Pre Bug Bash
- Define roles
- Pick up appropriate times
- Prepare test environment, database, credentials for different roles, and test scenarios
- Define a template to record bugs (Excel, Doc) where team can document their bugs
- Send out the invite
Roles
- Bug Master (QA)
- Decide test scenarios
- Assign test for groups
- Pre bug bash done?
- time decided?
- coordinator?
- Stager, invitation, note taking decided?
- Stager
- Setting up test env
- DB changes, application settings
- Invitees
- Doing the bug bash (Devs, QAs, BAs
- Note taker
- Gathering info regarding the bugs
Plan
- 5 minutes intro - test scenarios
- 40 mins - Group testing, note taker
- 15 mins - Bug triaging (valid or not) prioritising
Post Bug Bash (the 15 mins + post that)
- Clean up and triage the bugs
- Investigate on invalid bugs
- Prioritise the bug fixes for the release ![[Screenshot_2024-07-10_at_9.55.33_AM.png]]
How to prioritise?
- Severity → Impact to application (critical, major, minor, low)
- Priority → Impact to business (p0, p1, p2)
References:
Kroger Tushar Varma Hemalatha Thatigutla