1 / 1

Bugging issue and Reporting

A bad bug report would be one that isn’t filed in the right place. It may have useful, clear, and well thought out content but filing it in the wrong place isn’t the best way to communicate with a developer. An example of this would be sending a tweet or an email. http://www.maastrixsolutions.com

Maastrixsolutions
Download Presentation

Bugging issue and Reporting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bugging issue and Reporting What comprises a bad bug report? A bad bug report would be one that isn’t filed in the right place. It may have useful, clear, and well thought out content but filing it in the wrong place isn’t the best way to communicate with a developer. An example of this would be sending a tweet or an email. Tweets can turn into long chats about finer details. Emails are bad because bug reports aren’t the only things popping up in them. It’s overall an unreliable and decentralized way to send a bug report. What composes an even worse bug report? A bad bug report can be filed in the wrong place but still can be useful. A worse bug report would be one that doesn’t give enough information about the bug. If the developer receiving that report can’t even find and reproduce the bug, then it’s a horrible bug report. It’s as simple as that. Simply saying things like “It won’t work!” or “Fix it!” are worse than nails on a chalk board. That is where laziness takes a toll on bug reporting. Take the extra minute out of your life to explain the problem with a little more detail! Another trait that makes a bad bug report is when its priority is marked on the complete wrong side of the spectrum from the actual bug. If it’s marked as “critical” and its description is something along the lines of “This doesn’t toggle smoothly” then you might as well say goodbye to the organization of the developer’s team. This horrible practice throws simple UI disagreements in with serious problems like malfunctioning buttons which is totally misleading for the team. For More Informations http://www.maastrixsolutions.com

More Related