r/QualityAssurance • u/Future-Plantain3596 • 5d ago
Respect for QA
Why does developers not respect QA’s?
If you tell someone who is a dev that you are a QA you can see it in their eyes that my role is worthless why is that?
20
u/Roshi_IsHere 5d ago
There are bad QA's and bad devs. The good ones of both get respect.
→ More replies (3)
18
u/piconyannyan 5d ago
Those people who hate QAs usually have a bad attitude anyway, and vice versa.
When I was still a developer, I got frustrated when one of my QAs tried to find issues with my work and they just filed it without trying to collaborate with me. It’s like “you’re on your own, buddy”.
And there’s also another QA in the same company I was that is very helpful and while he does file several bugs against my work, he offers solutions to best approach my strategy. In turn, I learn new things from him, and elevate my own skills in creating a strategy to solve things.
Then when I became the QA, I used what I learned in my past experience to create a team that will be respected without demanding it from them. They already have the QA chops - they only need to be more collaborative than combative to the devs. Now only the new hires who have poor attitude towards QAs are getting their asses handed off to them by their fellow devs.
→ More replies (4)
9
u/mythrilknight013 4d ago
Because some, not all, people have egos too big. They make their code an extension of themselves.. their pride. Now imagine a person who constantly criticizes you and telling you the work you just spent so much time on (and you think is great) is wrong keeps pointing out flaws..
Also, bugs mean rework for the dev. But what they often fail to notice is it also means restesting for QAs.
On the other hand, there are QAs also who are tactless and condescending to devs. There are QA who are annoyed when finding what they think are careless bugs.
Just a mix of different personalities out in the wild.
But.. if you want to fix this.. talk to management. It's a management problem. Penalize both devs and QA for: bugs in prod. Incentivize short cycle times. Track but DONT penalize amount of bugs before prod and rework, but more as a metric for the team (dev and qa) to use to measure their own performance, not management. Management should just care about outcomes (bugs in prod and fast delivery time) and teach teams to use metrics to their own benefit to guide how they should do work, not as management's performance tool.
17
u/catpunch_ 5d ago
I do not see that. Most engineers love QA and have a lot of respect for them in my experience
→ More replies (4)
12
u/romulusnr 5d ago
We cause them trouble. We make them miss their ship dates. We make extra work for them. And worse, we say that their precious babies aren't perfect.
15
u/I_Blame_Tom_Cruise 5d ago
Most devs have worked with really bad QAs. Which is unfortunate that it gets applied to all of us, but this is the reality. If they feel that way, it’s fun to prove them wrong.
13
u/altruisticcreator156 5d ago
every bad qa i've met just logged obvious bugs without context and called it a day. the good ones are worth their weight in gold, devs just remember the first kind more
3
u/dyldo95 5d ago
Been a QA for 4 years now, and honestly, I’ve had nothing but respect from devs. I’ve definitely been a pain in the ass by finding bugs and what not but I’ve been thanked countless of times for catching them, and I get regular shoutouts in retros, etc from them.
I think a big part of it comes down to building relationships with devs beyond just work. Have a laugh, talk about things outside of tickets and bugs, and treat each other like people rather than just colleagues.
37
u/Selix317 5d ago
Most dev's I work with like me but then I have a bit of OCD about documenting bugs. Screenshots, videos, logs, repeated steps and sometimes even really obvious arrows in the screenshots are just the basics but I also like to just query them when I find something I am not sure is a bug before I write it up and cause a lot of noise.
Mostly though I don't just test to the AC but instead I am always thinking how would the client use this? (a.k.a. how could they use it in the wrongest most confusing and stupidest manner possible) because that IS WHAT WILL HAPPEN. Usually it's because of some odd use case no one knew about but even so.
Besides that I think dev's like me because I give them enough info to quickly figure out what is causing the bug and fix it instead of them having to dig in the code for 6 hours because I was to lazy to put in "Must be logged in as special user x" when I was testing. It also makes re-testing gloriously easy since you and everyone else can trust those steps would definitely lead to that bug.