testing

Writing good bug reports

3 Comments

Writing bug reports is a frequent task in the tester’s work. Here are my tips on how to write good and clear bug reports that properly underline: what issue can be observed, what behavior should have been observed instead, and how to reproduce it.

Continue reading Writing good bug reports →

automation, testing

Bugs and reproducing them

1 Comment

Whenever a new bug is found, the tester will need to create a defect in the defect tracking system they work with. This defect needs to contain clear steps to reproduce the problem, so that developers can identify the root cause of the issue. Here are some tips regarding bugs and reproducing them.

Continue reading Bugs and reproducing them →

automation

Java naming conventions revisited

Leave a comment

Let’s go way back to basics for a second: Java naming conventions. I wrote a post a while back regarding how to compose the name for various Java items, like classes or variables. In this post i want to emphasize the naming conventions, which relate to the use of upper/lower/camel cases when naming things.

Continue reading Java naming conventions revisited →

qa, testing

A matrix for when a bug only reproduces in one environment

2 Comments

This year, at several conferences, i did a talk on troubleshooting tips and techniques. One slide in particular seemed to be very much of interest for the attendees, so i decided to elaborate on it with a blog post.
In the talk, i was describing what to try to look for when an undesired behavior appears in the system under test, whose root cause is not very obvious. I also encouraged testers to participate in the process of finding the root cause of this bug, by providing a few tips and techniques that can be used. Continue reading A matrix for when a bug only reproduces in one environment →