<aside> 💡 Notion Tip: This template is a practical guide for engineering teams to find bugs in their projects. It's designed to be flexible, so you can adjust it to suit your project's needs. While it covers common scenarios, you may need to adapt it for your team's specific edge cases. Use this template to help your team systematically find and fix bugs.
</aside>
What do you want to accomplish in this bug bash session?
What are some known issues that bug bash testers should expect and not worry about reporting?
List of common edge cases that bug bashers should try to cover.
| Category | Testing Dimensions |
|---|---|
| Device | Desktop, Laptop, Tablet, Mobile, Wearable |
| Operating System | Windows, MacOS, Linux, iOS, Android, Other OS |
| Browser | Chrome, Firefox, Safari, Edge, Internet Explorer |
| Network | WiFi, Ethernet, 4G/5G, Offline |
| Localization | Language settings, Currency, Date/Time formats |
| User Role | Admin, Standard user, Guest |
| Accessibility | Screen reader, Keyboard navigation, Contrast settings |
| Authentication | Password, Multi-factor, Single Sign-On (SSO), Biometric |
| Data State | Empty, Populated, Corrupted |
| Performance | Load, Stress, Soak, Spike |
| Security | Permissions, Data encryption, Secure connections |
Here you can provide bug bashers with specific steps to ensure they’re testing correctly.
A database of all the bugs and feedback you found during your bug bash.