According to the flow chart, one doesn't need to "Look for an existing bug report before reporting the bug" if one doesn't like the software.
Seems like a pretty passive-aggressive way to punish the developers for a piece of software you don't like.
How to write a bug report that actually gets resolved – and why everyone should
11–18 of 18 posts
Re: How to write a bug report that actually gets resolved – and why everyone should
#12For example, an essential user action requires 3 cryptically named menu items, deeply hidden in 5 layers of menus, each of with takes ages to open.
Does that count as a bug? Users will simply fail at their job. But for many (open-source) developers, only a segfault counts.
I have stopped reporting such things.
Re: How to write a bug report that actually gets resolved – and why everyone should
#13After years of vague bug reports at various places we've worked, my 2 cofounders and I built a tool that records video of a bug, alongside network traffic and JavaScript logs.
That way even with a vague description, and no steps to reproduce, we can get a much better idea of what a customer is trying to report to us.
Would love for anyone interested to check it out: https://www.bugreplay.com
Re: How to write a bug report that actually gets resolved – and why everyone should
#14It's absolutely stunning how many testers I've worked with didn't understand the "Preconditions/Actions/Expected/Actual" as a bare minimum for a bug report. > Avoid using ambiguous words like “broken” or “not working.” Holy crap yes, this. So many infuriating waste of time bugs. And adding screenshots is good to call out. "X looks wrong", is useless, "X looks wrong " might still be useless, but at least you're trying…
It's absolutely stunning how many testers I've worked with didn't understand the "Preconditions/Actions/Expected/Actual" as a bare minimum for a bug report.
What I've never understood is how testers with multiple years of experience continue to get away with this. To me it's like checking in code that doesn't compile: you can't even do the bare minimum required by your job.
On the rare occasions I've had folks like that on my team, I've emphasized the importance of easy-to-replicate bug reports by pointing out that dev has to repro it in order to fix it, PM might have to repro in order to triage, another tester might have to repro in order to close the bug when you're on vacation, etc. Now, because of your shitty bug report, how much time has been wasted because your steps-to-repro are poor or non-existent? Me, I'm personally embarrassed when a bug comes back "no repro" because I half-assed the bug report.
Let alone getting into things like, copy-and-paste the damned call stack that's staring you in the face. And if you're a professional tester to whom we pay good money, and your "observed" includes "broken" or "doesn't work" with no further description, your future with this company might be in jeopardy.
Re: How to write a bug report that actually gets resolved – and why everyone should
#15It's absolutely stunning how many testers I've worked with didn't understand the "Preconditions/Actions/Expected/Actual" as a bare minimum for a bug report. > Avoid using ambiguous words like “broken” or “not working.” Holy crap yes, this. So many infuriating waste of time bugs. And adding screenshots is good to call out. "X looks wrong", is useless, "X looks wrong " might still be useless, but at least you're trying…
It's absolutely stunning how many testers I've worked with didn't understand the "Preconditions/Actions/Expected/Actual" as a bare minimum for a bug report. What I've never understood is how testers with multiple years of experience continue to get away with this. To me it's like checking in code that doesn't compile: you can't even do the bare minimum required by your job. On the rare occasions I've had folks like t…
I had a previous job where the testers would always do that, just report "broken" or "doesn't work" for just about everything.
I eventually figured out that they didn't actually want bugs fixed. They wanted to have lots of bug reports open and the application looking broken all over the place. Why? To justify the jobs and headcount and existence of the QA department. The QA managers would even resist movements towards automated testing, to protect their own turf and the employment of the far-too-many manual testers. I eventually got quite used to the disappointment in a tester's face when he had to close a bug report because it had been fixed.
Classic case of "if you're being paid for a problem, the last thing you want to do is solve it."
Re: How to write a bug report that actually gets resolved – and why everyone should
#16Earlier quoted context omitted.
It's absolutely stunning how many testers I've worked with didn't understand the "Preconditions/Actions/Expected/Actual" as a bare minimum for a bug report. What I've never understood is how testers with multiple years of experience continue to get away with this. To me it's like checking in code that doesn't compile: you can't even do the bare minimum required by your job. On the rare occasions I've had folks like t…
I had a previous job where the testers would always do that, just report "broken" or "doesn't work" for just about everything. I eventually figured out that they didn't actually want bugs fixed. They wanted to have lots of bug reports open and the application looking broken all over the place. Why? To justify the jobs and headcount and existence of the QA department. The QA managers would even resist movements toward…
I eventually figured out that they didn't actually want bugs fixed
Which is bulletpoint #2 in my presentation of "What Your Job as a Professional Software Tester Is". If you answered "file bugs?", my $29 PowerPoint deck will present you with ways to be a professional software tester instead of some hack who muddles his way through the day filing bullshit bugs because you'd never hack it as a dev.
Because the correct answer is: "get bugs fixed". Which means filing better bug reports, and thus it comes full circle.
Re: How to write a bug report that actually gets resolved – and why everyone should
#17I feel for you and the state of the QA industry. If you need someone efficient please contact me servicewareqa,gmail).
Re: How to write a bug report that actually gets resolved – and why everyone should
#18After years of vague bug reports at various places we've worked, my 2 cofounders and I built a tool that records video of a bug, alongside network traffic and JavaScript logs. That way even with a vague description, and no steps to reproduce, we can get a much better idea of what a customer is trying to report to us. Would love for anyone interested to check it out: https://www.bugreplay.com
Just dawned on me that a demo might be better than just linking to the marketing site :)
Here is a BugReplay recording demonstrating an ebay security vulnerability that we recorded awhile back:
https://app.bugreplay.com/shared/report/3efa632d-5b51-45f1-a...