Devs thinking they can replace QA with AI

I’m seeing more devs treat AI like it replaces QA. That’s when things go sideways.

Code ships fast. Nobody outside the developer stress tested it. Bugs get through that a second pair of eyes could have found before release.

Then QA gets blamed.

The reputation gets rewritten after the fact

Nobody says publicly, “we skipped QA on this one.” That would require admitting a decision got made. Instead, mentally, it gets filed differently. “QA missed this.” The reputation hit lands on QA, even on releases where QA was never in the room to begin with.

That’s not a small distinction. One version is a process decision someone made, ship without a second check, that they’d have to own. The other version is a performance failure, attached to a team that had nothing to do with the release. Nobody’s doing this maliciously. It’s just easier to blame a function for missing something than to remember it was never asked to look.

It runs the other way too

QA using AI to start writing code, thinking that makes them a dev now. Same mistake, mirrored. Producing code isn’t the same skill as owning what happens when that code meets production traffic, edge cases, and users who don’t behave the way the happy path assumed they would.

AI lowered the bar to produce something. It didn’t lower the bar to produce something good.

Anyone can generate code or test cases now. AI can’t judge whether that output is ready. Compiling successfully and surviving one run don’t prove much.

QA still owns the second check

I use AI for drafts and first passes. It saves time. It can’t replace someone trying to break the product before a customer does. Testers build that habit through years of checking happy paths, edge cases, and assumptions.

Developers who skip QA and testers who skip learning how software gets built make the same mistake. AI can produce output, but someone still has to own what it misses.