Transition of Bugs
Submitted by Rajachockalingam on Wed, 11/01/2006 - 22:38.
agile | extreme programming (XP) | taxonomy
I do testing in application which is developed under eXtreme Programming model. Due to the short span of the development process, we always work with bitter pressure. Whenever I encounter a bug, I immediately logged the issue in the tracking tool and if necessary I would made a face to face discussion with the developers.
I was recently testing an application which had an excellent search function. Most of the pages had a data grid with 4 to 6 columns. The point here I wish to mention is, the bugs identified is taking different weightage at different levels of development process. Within a period of week, the high priority bug becomes obsolete.
When I tested the application few days before release, I encounter a bug in the data grid. Each row of the data grid has a button to Edit/Delete the entire row. By clicking the edit button, we can make necessary changes in the details. In the latest build before release, I noticed a hyperlink (apart from edit/Delete button) for the entire row in the data grid which serves the same purpose of Edit/Delete button. I logged this in the tracking tool and considering the release date I rated it as “High”. I have been asked by developers to drop the issue since it is not going to affect any part of the application. Bugs are not only the missing functionalities; an additional functionality is also a major bug. I stick with my Bug and compromised with its rating (Medium). After a prolonged conversation, I was forced to drop the issue as a known bug by considering the time frame. The fact is, what I took as consideration to rate this bug as “High” becomes the same to neglect it within an overnight. I know this is a bug, don’t have any obvious document to prove it. Merely waste of time in argument. The question is: Is rating the bug is unnecessary in XP model? Why can’t we eliminate the rating of the bug? Can’t we think about some alternative? Feel free to drop your comment here else mail me.
I was recently testing an application which had an excellent search function. Most of the pages had a data grid with 4 to 6 columns. The point here I wish to mention is, the bugs identified is taking different weightage at different levels of development process. Within a period of week, the high priority bug becomes obsolete.
When I tested the application few days before release, I encounter a bug in the data grid. Each row of the data grid has a button to Edit/Delete the entire row. By clicking the edit button, we can make necessary changes in the details. In the latest build before release, I noticed a hyperlink (apart from edit/Delete button) for the entire row in the data grid which serves the same purpose of Edit/Delete button. I logged this in the tracking tool and considering the release date I rated it as “High”. I have been asked by developers to drop the issue since it is not going to affect any part of the application. Bugs are not only the missing functionalities; an additional functionality is also a major bug. I stick with my Bug and compromised with its rating (Medium). After a prolonged conversation, I was forced to drop the issue as a known bug by considering the time frame. The fact is, what I took as consideration to rate this bug as “High” becomes the same to neglect it within an overnight. I know this is a bug, don’t have any obvious document to prove it. Merely waste of time in argument. The question is: Is rating the bug is unnecessary in XP model? Why can’t we eliminate the rating of the bug? Can’t we think about some alternative? Feel free to drop your comment here else mail me.