What bug report must contain?
- What bug report must contain?
- Bug report content
- Troubleshooting
- Understand the scenario
- Break down the problem into steps
- Create specific, manageable tests
- Causes of problem
Bug report content
- Description
- Steps to reproduce
- Preconditions (to be an admin user)
- Actual result
- Expected result
- Attachments: screenshots
- Platform in which it is used
- Severity and priority
Troubleshooting
Example: You’re working on Google Chrome team and receive bug report: Chrome crashes on launch. What would you do?
Understand the scenario
The first thing you should do is ask questions to understand as much about the situation as possible.
- How long has the user been experiencing this issue?
- What version of the mobile app/browser is it? What operating system?
- Does the issue happen consistently, or how often does it happen? When does it happen?
- Is there an error message?
Break down the problem into steps
Now that you understand the details of the scenario, you want to break down the problem into testable units. Imagine, the flow of situation.
Example
- Go to windows start menu.
- Click on Chrome icon.
- Browser instance starts.
- Browser loads settings.
- Browser issues HTTP request for homepage.
- Browser gets HTTP response.
- Browser parses webpage.
- Browser displays content.
Create specific, manageable tests
Each components from second step should realistic. So, you can debug one by one.
Causes of problem
- Random variable: wrong input, autogenerate variable, or the time of day.
- Memory leak: memory overflow, recursion depth, heap overflow.
- External dependencies
