Re:How Going Back to Coding After 10 Years Almost Crushed Me
by xupybd on Wednesday April 07, 2021 @04:16AM
(#26721775)
I worked with a tester turned dev. He was amazing, his attention to detail and ability to grok specifications was second to none
Re:How Going Back to Coding After 10 Years Almost Crushed Me
by sumedh on Wednesday April 07, 2021 @07:50AM
(#26723473)
> Some of them are so bad
So why is your company hiring bad QAs?
Re:How Going Back to Coding After 10 Years Almost Crushed Me
by cassianoleal on Wednesday April 07, 2021 @09:38AM
(#26724729)
The answer seems to be in the same message:
> QA is considered a place for second-rate developers
Obviously, if you look for second-rate developers to be your testers, you will end up with second-rate testers or worse!
Re:How Going Back to Coding After 10 Years Almost Crushed Me
by tablespoon on Wednesday April 07, 2021 @10:55AM
(#26725830)
> Obviously, if you look for second-rate developers to be your testers, you will end up with second-rate testers or worse!
Yeah, and to make my thoughts a little clearer: if your organization does that, it's no wonder some people come to the (wrong) conclusion that only devs should test their own code. To come to the right conclusion in such an org, you either need an outlier experience (e.g. a talented tester who chose the role against organizational incentives) or the ability to see past your own direct experiences (which is really hard).
> There is an unwavering belief that knowing the corner cases and weak points of your own code makes you somehow better at writing the tests. We also seem to be obsessed with testing that is half-way between unit level testing and system level testing. We test APIs and features more or less in isolation.
You're both right. Devs should write tests for their own code, but they shouldn't be the only ones writing them.
One of the problems (at least at my employer) is QA is considered a place for second-rate developers. Some of them are so bad that they rely on the devs to basically write their tests for them, by requiring extremely detailed and specific acceptance criteria. Only once have I worked with a tester that was engaged enough to really understand the requirements on their own and call out weird behavior or corner cases that weren't spelled out in advance. It was great.