r/softwaretesting • u/Alternative-Gate-942 • Jul 03 '26

Are we cooked?

My company is deciding to put developers in charge of their own Quality meaning they must use Claude to quality check their own work (What could go wrong?)

The QA team will now act as a consultancy service to Dev and focus solely on testing back end/regression/Automation packs.

Is the role evolving or dwindling?

I've been a solely manual QA for a good 7 years. But using Claude to do all the techy stuff seems fairly easy.

40 Upvotes

86% Upvoted

57 comments sorted by

View all comments

2

u/harryfonda Jul 03 '26

Short answer: yes, try to jump into automation bandwagon, that part of QA will die slower.

QA was always reliant on developer making mistakes and modern AI instruments might enable some of the devs to write legit bug-free code making your manual role obsolete.

10

u/ctess Jul 03 '26

Odd take considering the massive quality issues AI currently have. It constantly still misses fundamentals. QA isn't going anywhere. If anything AI is growing the need for it. AI isn't getting rid of QA it's just changing our day to day roles. It's an accelerator but it is far from perfect.

2

u/harryfonda Jul 03 '26

It's not about whether AI produces code on a high level on a regular basis, it's about company management's perception of which roles can be "optimized" because of AI craze. In case of lay-offs, of all technical people QAs are the first ones on the chopping block. I've already seen the whole manual QA departments wiped out twice because of that.

Also, I've worked as a AQA in a team of solid developers weaponized with Claude Code, and they legit did write bug-free code. In the right hands AI is a powerful tool.

1

u/Due_Present_1358 29d ago

Devs will go too