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.
Bugs and reproducing them
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.
A matrix for when a bug only reproduces in one environment
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… Read More
The Little Tester – Stories in Testing #4
The Little Tester – Stories in Testing #3
The Little Tester – Stories in Testing #2
A bug is still a bug
Do you know this situation, when you implemented some automated tests based on a requirement, but a test has been failing for ages because a bug in the implementation was never fixed?
The Little Tester – Stories in testing #1
The Little Tester – Stories in testing #0
The tester’s daily dilemma: my automated tests fail because of the test environment. What can i do?
Automated tests. They are there, and they need to be run. On a test environment. By you. You wrote them in a way that they should be reliable, when the features under test work as designed. But each day you run the same tests on the same test environment, and they fail. Not because the… Read More
imalittletester 