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.
This Software Testing Help article asserts that bug reporting and tracking is an art and emphasizes the importance of mastering this skill. A bug report is a collection of bad news about the shortcomings of an application or project, so the way you present it is crucial. Take a look at the full article for a list of considerations you should keep in mind when reporting a bug.
For many software development teams, especially agile ones, attracting diverse individuals is of the upmost importance, mainly because it can lead to effective collaboration and improved product quality. I mean, the more people, the better, right?
There does come a point, however, when teams simply become too big to manage, and this can negatively affect progress across all active projects. So how do leaders determine when they’ve hit their optimal staff number? This post examines situations in which teams become too big and explains how you can make your testing team as effective as possible with the employees available. Check it out!
Testers and Developers—this match up can result in some tension, but it’s time to push past all the antagonistic images and comments of the tester/developer relationship and strive for tighter collaboration and better working rapport between these groups.
This presentation from Karen Johnson identifies seven specific areas to build collaboration during the development and testing of a product. She also explains how having an empathetic approach can improve this relationship between testers and developers. Watch the full presentation here.
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!