Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@intoleRANT I am QA (SDET) former embedded dev.
I guess it's just the general lack of understanding towards the importance of testing, automation and iterative validation that cause these sorts of issues.
When I was a dev, I hated the fact that many people considered testing as a second hand type of engineering and just openly shat on it. -
@PepeTheFrog yes, that was exactly my feeling too. It felt like there was hostilities between dev and QA but we were both on the same team. No one really told me how important testing was, but I assumed I'd I found a bug the devs might want to know how to reproduce it. But that could just be because I'd already learned how finicky computers are and that maybe my hardware was the issue, not their code.
when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
Go big or go home.
So what's up with some devs, QAs and managers that create bug tickets with little to no information on what is the actual bug? I can semi-understand in the case where you document it only for you to read later.
Fuck you if you think that a ticket with only a title saying "fix all the bugs for this release" or "this feature is not working" is an appropriate way of documenting a bug.
Fuck you even more if when you are being asked to provide more info to reproduce the issue so someone else can actually be sure it is fixed or not (environment, steps, expected result, actual result, etc.), you simply say that you don't have the time for it and documenting tickets is a waste of time.
Hiring YOU was a waste of time!
rant
bug report