Posts Tagged ‘bugs’

The First Bug Martin Jansson 2 Comments

Last week I entered the first bug in a bug system for a new service that I just started to work on. Me and my team spent quite some time in getting it right, setting the standard for bugs to come. If the first bug is crappy, the rest can be as well. We considered […]

It’s the little things Martin Jansson 2 Comments

As a tester you find lots of things that bugs you when exploring a system. In some cases these issues only nudge you slightly at first, but after passing over the same issue many times it really starts to drive you crazy. This, at first small issue, has now become something that affect you more […]

Bug Magnets are thinking as criminals Henrik Emilsson 8 Comments

I know of some testers who are pointed out by others to be Bug Magnets; people recognized for their ability to somehow draw bugs to them. Bug Magnets can be found in many workplaces and I bet that you know of someone that falls under this description. I have been appointed a Bug Magnet by […]

Testing Clichés Part IV – We can’t find all (important) bugs Rikard Edgren 4 Comments

It’s a truth that we can’t find all bugs, but is it really a truth that we can’t find all important bugs? And it’s a cliche when used as answer to the (sincere) “why didn’t you find that bug?” question. Testers are paid to find important information about what they are testing, and included are […]

Rage against the machine Henrik Emilsson 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 […]

The power of a sound Martin Jansson 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. […]

Broken window theory and quality Martin Jansson 6 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. […]

The impact of a good or bad bug report Martin Jansson 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 Rikard Edgren 3 Comments

This post was triggered by blog post 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 […]

Resolved as Not Repro Henrik Emilsson 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 […]