A rookie tester’s guide to making the arrest

Bug Investigations

Thousands of words have been written about the investigation part, and it’s usually where the information ends.  You’ve got a crack bug investigation procedure.  You’ve clearly identified your oracles, you’ve mapped your coverage, you know your quality criteria.  You’ve been patrolling the mean streets of your pre-release build, and you’ve noticed something out of the ordinary.  The adrenaline starts pumping, and you’re ready to reach for the red and blues.  We wanna take this perp down.  But hold up, bronco.  Before we grab the pepper spray, let’s talk about what happens after you have a suspect in your sights.  You’re pretty sure you want to make the arrest, but we don’t want to compromise the sentencing later.

Continue reading

Our first Defect

So we had our first defect raised. On the Chrome browser the RSS link above right doesn’t seem to work and complains about a missing style sheet. I’ve tested it on IE8, FF4 and Safari and all work just fine. So I’ll just put this down to “Google….get that fixed!”  😉

So sorry guys, if you want the RSS on Chrome, use something else for now.

But apart from that can I say I just love the testing community!!! You actually get feedback. Feedback is the only and -in my opinion- best way to learn. As a tester it’s what we do. We just put our foot in it wherever we can. I try and train my skills wherever I am so I of use feedback buttons on websites and do report issues with software. And the amazing thing is, that it works. Things do get fixed and companies, OSS projects, web masters,… they do react and they gladly do so.

So if you’re out there and see something you don’t like. Don’t click to the next page. Complain, rant, feed back but remember always to be rational, explain in detail and state the context. You will see that it works and that you’ll have trained your skills.

Author: Oliver