Logging Bugs: Do's and Don'ts


Bug's Life Cycle
Bug's Life Cycle - [Image source: http://www.bughost.com]

As a tester tests an application and if he/she finds any defect, the life cycle of the defect starts and it becomes very important to communicate the defect to the developers in order to get it fixed, keep track of current status of the defect, find out if any such defect (similar defect) was ever found in last attempts of testing etc.
How to report a bug?It’s a good practice to take screen shots of execution of every step during software testing. If any test case fails during execution, it needs to be failed in the bug-reporting tool and a bug has to be reported/logged for the same. The tester can choose to first report a bug and then fail the test case in the bug-reporting tool or fail a test case and report a bug. In any case, the Bug ID that is generated for the reported bug should be attached to the test case that is failed. Tagging or naming the bug with the Unit or integration test will aid developers to find and analyze bugs more effectively and efficiently.
When to log items?
  • Do log everything. Be very verbose when describing/reporting bugs. It might seem important to you, but this will hep developer to find bugs much quickly. Just because the bug may seem trivial or simple or only happen 'every now and again' does not mean that it should be ignored.  Even it you are not sure it is an issue, LOG IT.  Better to have close off an non-issue then fail to report a major bug in hiding
  • Do include screenshots of any error. This is very important in diagnosing an issue and may be the only aid in cases where bugs cannot be replicated (rarely)
  • Do attached error logs or stack trace  (if any) when logging bugs.
  • Don't assume that someone else is going to fix the issue.  Also, don't assume this issue is too trivial or minor to report.  Wouldn't it suck to find out after the application went lived that you failed to report a critical bug because you thought it was not a 'big deal'?
Providing information on the log:
  • Do provide detailed information about the bug.  Save yourself the headache later and provide as much information as you possible can.  This should include, but not limited to items such as Build Version, Environment, Platform, Short Description of issue, Severity, Detailed steps to reproduce.
  • Don't make provide a single sentence that says something like 'Unable to perform XYZ in the ABC process'.  This type of information will provide nothing of real value to the next guy.  Sure, this would be a great line for the title of the bug.  But by no means is this enough information to fix the bug.
What types of items to log:
  • Do Log Everything.  Enough said
  • Don't make assumptions
When to log bugs:
  • Do log them as soon as possible.
  • Don't put it off.  If you dont log the bug as soon as you find it you WILL forget something about what you did to cause it.  For the sake of your fellow co-workers log it now before you forget.


When in doubt, be verbose - Ferron Hanse
Some content presented was adapted from several sources. A list is included below.


http://devlicio.us/blogs/derik_whittaker/archive/2007/08/19/logging-bugs-the-do-s-and-don-ts.aspx
http://www.buzzle.com/editorials/4-11-2005-68387.asp

Comments

Post a Comment

Popular posts from this blog

JavaScript Module Pattern: 2 Forms

JavaScript Module Pattern: 2 Forms The module pattern is a common JavaScript coding pattern. It's generally well understood, but there are a number of advanced uses that have not gotten a lot of attention. In this article, I'll review the basics and cover some truly remarkable advanced topics, including one which I think is original. In the following guide I will explain two different variation of module pattern that I use during development, namely: Loose Augmentation Function Import Augmentation One limitation of the module pattern so far is that the entire module must be in one file. Anyone who has worked in a large code-base understands the value of splitting among multiple files. Luckily, we have a nice solution to  augment modules . First, we import the module, then we add properties, then we export it. Here's an example, augmenting our  MODULAR  from above: // global object being added to the user space var modular = ( function (
Read more

Pseudo-Random UUID Generation with mask support

There are a lot of cases where we may want to generate a pseudo- random universally unique identifier ( UUID ) , sometimes called GUID . I previously wrote an article on creating Pseudo Random numbers in JavaScript, which generates a uuid of length X where x is a numeric value supplied. http://pragmatic-coding.blogspot.com/2012/01/javascript-pseudo-random-id-generator.html The problem with the above generator is that is does not allow developers the flexibility of specifying the format of the uuid as shown below: 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxx0' 'xxxx-xxxx-xxxx-4xxx-yxxx-xxxxxxxxxxx' 'xxxxxxxx-xxxx-xxxx-yxxx-xxxxx-xxxxxx' Above I’ve shown you 3 different uuid formats that 3 different developers wanted, so an algorithm had to be devised that allow developers the flexibility of changing the data formats. One other thing to note about the above is the x values, which represents the values you want to be randomly generated. All o
Read more

Mocking Ajax with the JQuery Mockjax Library

Unit testing your JavaScript code to ensure everything works according to plan is a very important and tricky business. Properly testing code bits can save you a lot of time and money. This article focuses not on the general topic of unit testing JavaScript, but more specifically unit testing JQuery Ajax functions. HTML File for the Test. <! DOCTYPE HTML > <html>     <head>         <link rel = "stylesheet" href = "lib/qunit.css" type = "text/css" media = "screen" />         <script src = "lib/qunit.js" ></script>         <script src = "lib/jquery-1.7.js" ></script>         <script src = "lib/json2.js" ></script>         <script src = "lib/jquery.mockjax.js" ></script>         <script src = "mockjax.js" ></script>         <title> MockJax Tests - </title>       </he
Read more