Still Life

A Series of Mental Snapshots

Posts Tagged ‘Bugs’

Bugs in the Wild: The Paradoxical Error Message Edition

Posted by Steve on April 23, 2009

A friend recently sent out a screenshot of a quite humourous error message. He was attempting to free up some space on a network drive, by deleting some files, when he received this less than helpful error message:

Error message that appeared when deleting a file

Error message that appeared when deleting a file

The text in the error message is:

Cannot delete week4: There is not enough free disk space.
Delete one or more files to free disk space, and then try again.

It can be seen that this is a faulty error message, and something else is really afoot; one cannot delete files if one cannot delete files.

An interesting question here is why this error message came up? Is this the actual reason the file cannot be deleted, if so a different error message should be displayed so as not to confuse people. If this is not the cause of the issue, then why did this message get displayed?

–Steve


Posted in Bugs in the wild | Tagged: , , , , , , , , , , , | 1 Comment »

Bugs in the Wild: WordPress Total Views

Posted by Steve on February 21, 2008

There was a bug that I noticed today (as well as in the past few months) right here in wordpress. There seems to be an issue with the ‘Best Day’ and ‘Total view’ count on the blog stats page.

As can be seen in the attached picture, it says that my best day was ‘ Saturday September 23rd 2006’. This is impossible since I did not start this blog until September 2007. Furthermore the Total view count is terribly low, it is marked as 35, when I know for a fact I have many times received 35 views in a single day.

I find it odd that this bug has been present for about 2 months or so now. The problem is intermittent though. I have seen days were it actually has been fixed and does display the correct numbers. I also am very curious as to how they calculate those numbers, because all of the information is available from different sources. There is a graph that displays page views per day and there is also a section where an actual count is given per post that you have made. It seems odd to me that these functions work properly but the one mentioned above does not. It just shows that because one similar feature works does not necessarily mean that all the related others will.

–Steve

PS: I have done a little research and it appears tickets have been opened to let wordpress know of the issue.

wordpresserror.jpg

Posted in Bugs in the wild, Testing | Tagged: , , , | 1 Comment »

Dealing with Bugs…

Posted by Steve on November 21, 2007

Filing Bugs / Bug Scrubs
—————————-

I have been giving thought to how bug scrubs go and it seems like there is some room for improvement. From what I have seen bug scrubs are done every day and they last about an hour, and have ~4-5 people in them. Say at an average of 40$ an hour, it wastes about 1000 dollars a week (which I guess isnt terrible) but there are bug scrubs for each product, so say 3-4 products we are up to 4000 dollars a week, which equates to about 200K a year, now we are talkin! Other then the money this wastes TIME, time that could be spent testing, developing, getting the product out the door etc… It just seems that there is a more efficient way to go through bugs. So I gave it some thought and came up with a possible algorithm.

The plan I came up with is as follows:
——————————

At the beginning of the test cycle introduce a few key things. I am going over what to introduce and what I think that would accomplish

The Testers and developers should know each other.
–> Face to face communication(encourage through a meeting with all developers and testers) can save a lot of misunderstanding and time.
–> When people know who they are working with they are more likely to work harder (because they know what they are working for).
–> Might result in more collaboration and idea sharing. Also a better team environment.

Testers should also know what area each developer works on.
–> This will allow a tester to assign a bug to a certain developer, and skip the bug scrub step for that bug
–> Less bugs in bug scrubs means less wasted time.

The Developers should know the testers
–> If a tester files a bug that they think is by design, they can face to face with the tester to find out if that is correct or not
–> If there is a disagreement, it can be placed in with other cases to be scrubbed.

How to assign Priority of Cases should be clear
–> If the priority of cases is clear, testers can assign priority on their own.
–> If the tester is not sure they can assign it to the developer and he can assign priority based on his thoughts
–> If the developer does not know, then it can go to the unscrubbed pile

Developers should be clear on what they desire in Bug reports
–>when are diags needed, when are stack traces needed, is a video always good?, should there always be screenshots?, what level of detail is needed?
–> This will allow for greater efficiency because no information will be missed (for example, I missed a stack trace that was needed once, simply because I didnt know I needed it)

I think that putting these processes in place could help do the following

–>Build a better sense of fellowship between developers and testers

–>More efficiency in bug resolution and bug scrubs

–>Less bugs to go through in bug scrubs

Any comments are always welcome

–Steve

Posted in Testing, Work: General | Tagged: , , , , , , | 2 Comments »