How to Create an Effective Bug Report That Actually Gets Resolved Brian Pugh VP of Engineering Lucid Software McKay Christensen IT Engineer Lucid Software
How to Create an Effective Bug Report That Actually Gets Resolved
Brian PughVP of EngineeringLucid Software
McKay ChristensenIT EngineerLucid Software
Agenda
1. What Defines a Bug?
2. The Best Way to Report a Bug
3. Why Everyone Should Report Bugs
4. What Every Bug Report Needs to Include
5. Example of an Actual Bug Report
1. What Defines a Bug?
User vs
Developer
1. What Defines a Bug?
2. The Best Way to Report a Bug
2. The Best Way to Report a Bug
3. Why Everyone Should Report Bugs
3. Why Everyone Should Report Bugs
Show support for the software
3. Why Everyone Should Report Bugs
Show initiative
4. What Every Bug Report Needs to Include
Try to reproduce the bug to make sure it is indeed a bug.
Step 1
Check if the bug has already been reported:
Direct Google Search
Software Bug Reporting Page
Do not create an additional bug report
Step 2
Report the bug or make a comment on an existing bug report. Include the following:
Descriptive Title
Environment
Expected Behavior
Actual Behavior
Steps to Reproduce
Demonstration of Bug
Step 3
Be proactive and follow up!
Step 4
Bug Reporting: 4 Step Process Recap
Step 1Try to reproduce the bug to make sure it is indeed a bug
Step 2Check if the bug has already been reported
Step 3Report the bug (or make a comment on an existing bug report
Step 4Be proactive and follow up
5. Example of Actual Bug Report
Q&A | #BugReporting
Thanks for joining us!
Brian PughVP of EngineeringLucid Software
McKay ChristensenIT EngineerLucid Software