Mouse Smash

JC Lau's blog about geekery, gender and other rants

Adventures in QA: Chapter 3: A bug’s life

Leave a comment

It’s been a few weeks since I’ve been doing this QA gig and it’s not as terrible as I thought it would be. Okay, the work is still quite grunty and below what I was previously making, but it does have its moments where it’s okay.

The main thing we’re supposed to do is log bugs. When I first applied and got asked on the interview questionnaire to define what a bug was, I think I actually wrote something technical about how something does not operate to specifications or something, but to be honest it’s more like “any kind of weird shit that randomly pops up” since literally it could be anything that’s not working properly.

bugcycle

The life cycle of a bug.

There’s a process (also known as a life cycle) that you go through to log bugs: basically you find it, figure out how to reproduce it (usually if you’re going through a certain process you just repeat it and see if it happens again), then you describe the problem and how it should be fixed, and it gets sent off to someone else (in Triage) to deal with. Triage is basically responsible for checking the issue and sending the bugs to the right place. After it does its rounds getting fixed or whatever, you get it back and have to verify that it has actually been fixed. If it has, you close the bug. If it hasn’t, you go around again.

Then, after that’s all done, you rinse and repeat as you find more bugs. Fun times.

Of course, it’s not challenging in the conventional sense of the work, but I actually quite like this sort of thing, because there’s a lot of pedantry and memorizing.And, with any game of “spot the difference”, there’s some satisfaction when you catch something that’s already supposed to be vetted.

Also the life cycle of a bug.

Also the life cycle of a bug.

That said, testers are at the bottom of the totem pole, or pretty close to it. There’s triage, and then some devs/engineers, and at any step of the process they can knock your comment/buglog back if they don’t think it’s an issue. And at that point, unless you feel really strongly about it, you’re just supposed to deal with it and move on.
That said, finding the right level of pedantry can be pretty hard. You need to have bugs logged so it looks like you’re doing work, but you can’t be going around making too much trouble. I got told off because I was logging Oxford commas in the text, which, technically, was the right thing to do (according to the style guide we were given), but Triage came back and said “Stop it, nobody cares”. And yeah, not pissing off the people in Triage is a good idea. So there’s quite a bit of trial and error to get the right amount of bugs in circulation, and then once that’s set it’s an issue of maintaining it.
One thing that bothers me is when people use the verb “bug” to mean “log a bug”. It’s probably the pedantry talking, but when you say “I’m bugging this problem” I imagine that you’re actually just annoying the crap out of the problem. I know this isn’t a battle I’m going to win but I can’t help but get an eye twitch when people say it. Ugh.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s