The Manual Tester Role Is Dying. I’m the QE Lead Who Stopped Defending It.

Description and use

The QE lead at pdf.net eliminated manual QA, making developers test their own features and adopting automated testing. This sped up releases, increased test coverage, and improved production monitoring while keeping the team size unchanged.

Problem

Manual QA was ineffective, costly, and invisible, leading to slow releases and missed bugs.

Outcome

The transition eliminated the manual QA queue, increased test coverage, maintained release frequency, and improved visibility of production issues without reducing team size.

Workflow

• 1. Developers test their own features before release.
• 2. QE reviews and approves tests written by developers.
• 3. Automated test suite runs on every merge.
• 4. QE monitors production signals, logs, and analytics.
• 5. QE fixes bugs in production when within reach.
• 6. QE presents metrics and impact to business during demos.

Evidence

We used to spend our days checking tickets. Now we dig into production data, fix some bugs ourselves, and build a test suite the whole engineering team contributes to.

Source

The first was the escape hatch. When there’s QA after you, you always have a way out.

Source

In the first month, we brought teams dozens of real bugs our old process missed.

Source