3 ms·
I wonder if it's improvements in automation or if QA responsibilities are increasingly rolling up into standard developer roles or because the line between QA a
by weberc2 7y ago
I wonder if it's improvements in automation or if QA responsibilities are increasingly rolling up into standard developer roles or because the line between QA and dev is blurring (e.g., software testing now requires stronger dev/automation skills so the QA job looks more like standard software engineering)?
- ivan_gammel 7y agoI don't think automation or shift of testing responsibilities to developers is harming QA role in any way, it's just the first candidate for layoffs, because it does not have immediate impact on business. Independent SQA is still relevant, even it it becomes a developer specialization.
- weberc2 7y agoThat wouldn't explain the perceived increase in QA layoffs; you would need something else, such as worse economic conditions.
- xemdetia 7y agoI agree with the concept that it is turning into something else, as I see DevOps/SRE/CI/PM people doing QA work through trying to just make the thing go. It just is leaving a lot of gaps in longevity, complex setup, and building tests either manual or automated to do that better. In the last dozen or so teams I've interfaced with this is just getting worse as I'm seeing lots of situations where things like backup/restore breaks from the last hotfix, upgrade a system a few sequential versions, and only covering X-1/X critical features in ordinary testing. These are things that a traditional QA team would cover after it burns the business/org in one way or another, but since it's not a core focus of some of these people covering parts of the same role it's leaving a lot of not-obvious gaps in a lot of groups.
- thrower123 7y agoDevelopers are just turning into glorified hatracks at this point, and the results are discouraging. It's no wonder that people burn out when they are expected to do ever more and more with less.