3 ms·
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 th
by T-hawk 10y ago
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."
- mikestew 10y agoI 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.