Bug Reporting is an Art – Idexcel Testing Roundup

1. Why Bug Reporting is an Art That Should Be Learned by Every Tester

When it comes down to it, a tester’s primary responsibility is to test an application or project and report back on the issues. But it isn’t here that the responsibility ends, from here, the real work begins. It’s absolutely essential for testers to understand why their bugs are being rejected or being marked as “not reproducible” and how to react in these situations. Read more…

2. How Was This Tested?” Providing Evidence of Your Testing

Many testers have a tendency to minimize the information they record when testing. The challenge comes when problems are found later, possibly after the software is in production. How do we remember what we did, and when? What records do we have to refer to? How do we, as testers, answer the question “How was this tested?” Read more…

3. The Advantages of Utilizing Formal Test Design Techniques

When it comes to test design, there are those who firmly believe in the use of formal test design techniques and those who believe that those same techniques cause rigid thinking and limit creativity. I believe formal techniques have value as a basis for formal analysis and design as well as for creative thinking. Read more…

4. Discussion: Should Trivial Bugs Be Logged?

A poster to the Test Huddle forum referenced this blog from Eric Jacobson in which he argues that reporting trivial bugs tends to waste everyone’s time and that testers shouldn’t log them. The forum poster’s question: Do you agree or should all bugs be logged despite the severity?

Reponses from both sides have already been submitted to the thread. Contribute your own thoughts on the matter here!