Can Developers Really Absorb the QE Function?

I called a senior quality engineer because I wanted to put together an article about why companies should think twice before eliminating dedicated QA teams and moving testing responsibilities entirely to developers. I ran across two firms over the last quarter that are making that same move….

She laughed and said, “Have you asked a developer if they even like testing? They barely do their unit tests.”

Lol.

Then she told me it was funny I had called because she’d actually been noticing signs at her own company that they might be heading in that same direction. She was even starting to think about what that could mean for her next career move.

Talk about coincidental timing.

I asked her what she thought were the biggest risks companies take when they expect developers to absorb the QE function.

Here’s what she shared.

1. Developers are focused on making things work. QE is focused on finding ways they don’t.

There’s a difference between validating that your code works as intended and actively trying to break it.

She described situations where developers hand code over to QE without checking even the most basic functionality themselves. If those fundamentals aren’t being tested, it’s unlikely they’re consistently thinking through negative scenarios, edge cases, unexpected user behavior, or ways the application could fail.

QE brings a different mindset. It’s not just about confirming a feature works. It’s about challenging assumptions and finding what could go wrong.

So what I gathered from her overall point is that actively thinking about how to break something, rather than just making sure it works, is a mindset that doesn’t necessarily come naturally to every developer. If companies shift testing entirely to development, they risk overlooking scenarios that could lead to more bugs making it into production, ultimately impacting the product and the business. And I’m also seeing examples of companies reassessing that approach to quality. Take UKG, for example. After cutting QA teams about a year ago and shifting work to developers, the company hired a Director earlier this year to build out its QA Center of Excellence (CoE). What measures are these companies taking before deciding slashing QA is the best approach?

2. Testing individual components isn’t the same as understanding how everything works together.

Unit testing is one piece of the testing lifecycle. There’s a much bigger picture that includes integration testing, end-to-end workflows, regression, smoke testing, and application stability.

Her concern was that developers aren’t necessarily thinking about that entire testing methodology. They’re focused on their code and the functionality they’re building, while QE has to consider how all those pieces interact. A feature can work perfectly on its own and still create problems somewhere else in the application.

3. Testing is a discipline, and knowing how to use AI doesn’t automatically make you good at it.

I asked her why developers couldn’t just learn the different testing methodologies and use AI to help them. That is after all what I see some leaders mindsets being as they make decisions around testing teams.

She agreed they could, but said it would take a genuine interest in learning the discipline and time. She gave me an example from just that day: She asked Claude to generate smoke and regression tests. Instead of producing what she was looking for, Claude went into the repo, found existing unit tests, and pulled those into its response. She had to go back and forth with it, explain what she wanted, and train it on what the tests should actually look like. And even after that, she was finding gaps. Her point was that AI can help generate tests, but you need someone who understands testing to recognize when the output isn’t right, identify what’s missing, and know how to improve it.

Additionally, she mentioned that even some of the newer developers on her team are being trained in testing and still struggling.

What I gather here is seeing testing as it’s own technical discipline to master.

So what are the signs she’s seeing at her own company?

I asked her because I knew her team had just hired another QE. Why would they do that if they were moving another direction?

Apart from one of the indicators provided above, she explained that the transition seems to be starting with some of the more mature teams. Her own team is newer, moving quickly, and still adding headcount. So while they’re continuing to grow their QE function, she’s watching how things are evolving elsewhere in the organization (process being shifted, testers being tapped for development chairs etc)

As recruiters, we’re having conversations with people who are experiencing these changes firsthand. I think it’s worth sharing what we’re seeing in the market.

Never Miss a QA Post

Get the latest posts and tips delivered straight to your inbox.

I don’t spam! Read my privacy policy for more info.

Leave a Reply

Your email address will not be published. Required fields are marked *