Posts Tagged ‘bugs’

Rage against the machine March 2, 2010 5 Comments

As a user of Facebook I feel really helpless when nothing works as it should (as was the case with the latest GUI-update). Posts were stochastically shown in the feed and a lot of errors occurred in various situations. A lot (all?) of my friends on Facebook experienced the same problems.
When there are lots of [...]

The power of a sound October 16, 2009 1 Comment

In my local food store they have this system where you scan the price tags on the food you buy and most often smoothly able to pay and exit without having to stay in any long queues.

A time back they must have changed software in these scanners because their behavior changed and bugginess increased. The [...]

Broken window theory and quality August 18, 2009 5 Comments

Consider a building with a few broken windows. If the windows are not repaired, the tendency is for vandals to break a few more windows. Eventually, they may even break into the building, and if it’s unoccupied, perhaps become squatters or light fires inside.
Or consider a sidewalk. Some litter accumulates. Soon, more litter accumulates. Eventually, [...]

The impact of a good or bad bug report July 18, 2009 4 Comments

You are on a quite large company where there are several QA divisions, several layers of management, several listeners to each step of the development process. It is the final weeks of the release. You are about to enter a bug which seem serious but you are not sure. You can take at least two paths [...]

The Importance of Resolution in Bug Systems June 12, 2009 3 Comments

This post was triggered by blog post Resolved as Not Repro - http://thetesteye.com/blog/2009/06/resolved-as-not-repro/
I believe that bug systems too often are used with onlý a this-project-right-now approach, where you care most about just getting all items dealt with.
This is perfectly fine for one-off type of projects, but does not work fully for software where the bug system [...]

Resolved as Not Repro June 9, 2009 8 Comments

Lets say that you have a bug system; and for each bug you have the two fields “State” and “Resolution” where the following values are valid:
State: New, Assigned, Resolved, Closed.
Resolution: Fixed, Invalid, Won’t fix, Duplicate, Not Repro.
Further, you have a field where a product version number should be entered; i.e., the earliest version number of [...]

Unwanted bug reports May 3, 2009 4 Comments

A few months ago I reported a bug to the installer of a security radar at a door. He had placed a radar just inside the door so that people who were going out never had to use their pass card to get out. Instead you just walked up to the door and it opened, [...]

Decisions around the product release – part 3 April 17, 2009 2 Comments

What is essence of the discussion on release team/showstopper meetings?
I am assuming that there is a meeting. I’ve been to many different kinds of showstopper meetings and most companies handle them differently. One important item on the agenda for the meeting is usually the bugs that are found late in the project, thus at the [...]

Impeccable bug taste? April 14, 2009 2 Comments

It cannot be exactly defined what a bug is, or how it should be reported. And each tester, developer, project manager et.al. has her own way of writing, thinking about and handling bugs.
I like to think of this as taste.
Do you prefer having all details in a bug report, or only including what you think [...]

The Superstitious Bug Reporters April 25, 2008 1 Comment

I have a friend that proof-reads every bug report before reporting; “otherwise there will be spelling errors”, she says.
I have a friend that always reproduces the bug before reporting it, at least four times.
I have friends that always ask “Bug or Feature?” or “One or two bugs?” when they are uncertain.
I have friends that look [...]