Everyone is talking about how fast AI writes code. But what happens afterward?
A report came out, State of AI Generated Code 2026that asked 300 testing and quality professionals how they're doing with AI-generated code. And what they say isn't what you hear in productivity talks.
In the video I go over what caught my attention the most: what happened with bugs, what happened with the QA workload, a piece of data about trust and regressions that changes how you think about testing scope.
And tell me: does the same thing happen on your team, or is your experience different? I'll be reading your comments, and I'm also leaving you the link to the report.
If you're interested in AI, I invite you to the course Introduction to AI systems testing.
Frequently asked questions
What is the State of AI Generated Code 2026?
It's a report that asked 300 testing and quality professionals how things are going with AI-generated code.
Which topics from the report do I cover in the video?
What happened with bugs, what happened with the QA workload, and a data point about trust and regressions that changes how to think about test scope.
Keep reading: When the tester goes from executor to orchestrator and Tools change, testing fundamentals don't. If you want to go deeper, I recommend the course Introduction to software testing.