POST
Sunday sermon #1 - QA, goalkeeper of every developer
Wait, what?
Yeah, your goalkeeper. Surprised? If you are a developer there’s a great chance that you are underestimating the role of QA in development process. The less experience you have the more the chance is. But hey, that’s natural you know.
You will grow to love them on your first major, ekhm, bug on production.
Bugs on production never happen to me!
Maybe, or perhaps you just ignore the pingpong you usually play with your QA tester. Acceptance criteria not fulfilled? Meh. Bugfix still not resolving the issue? Pfft, what do they know. Hard copy change? Ah come on man, that’s just one word off.
Every time your QA dared to make you sit down and amend the mistakes - they saved one bug on production. Not you, them.
Okay, I may have had one or two bugs. But hey - it’s QA not catching them
Come on. That’s low. It was you in the first place who introduced the bug. A moment ago you were close to completely disregarding QA work, now you try to blame them for letting a bug go through the testing.
Sure, it would be nice to fix the issue before it getting to production but man - it happens everywhere, regardless of development process.
B-but such minor quality issues shouldn’t be considered bugs
Oh but they definitely should. Every single issue released to production is potentially harmful to the company you are working at. I do know you are but a mere developer but hey, it is going to be you talking with your manager next time QA fails to catch something.
After all the clients whom pay your company pay your salary as well as your manager’s.
All they do is writing automation tests, I could do it myself
Sure you could, you are a developer after all. And by such you tend to write things as you understand them. Automation testers however write them as per business requirement totally ignoring the idea you came up yourself. Often mismatching what you have developed and, again, defending the goal.
This point however could be indeed true if you yourself began writing behavioral tests. But hey, I bet that’s boring.
So what should I do to not mess with QA then?
Just don’t be egocentric, that’s all. If you are not a junior it’s going to be way easier for you since you should already know that - don’t take everything personally.
You guys both work for the same goal, don’t forget that.
Afterword
Turns out it’s a lot of fun to write short, clickbaiting (sorry, but not really) posts like that. I will try to keep them as series - sunday sermon seemed to fit as the name like nothing else.
If you do like this form of writing - let me know in the comments. Hell, even if you don’t just let me know.
Cheers, Tomasz