This article is based on expert commentary originally published on TechRepublic (2017). Attribution to Chris Marsh (AKQA), Greg Hoffer (Globalscape), Rupinder Singh (Software AG), and Mark Doyle (Collabroscape).
Automation and QA: Not the Same Thing
A common misconception in DevOps is that rising levels of test automation will eventually make QA engineers redundant. The logic sounds reasonable on the surface: if machines can run thousands of test cases faster and more consistently than humans, why maintain a dedicated QA function at all?
The reality is more nuanced. Automation handles the mechanical execution of tests, but it cannot replace the strategic thinking, contextual judgment, and user empathy that skilled QA engineers bring to the software development lifecycle.
“Test automation may largely eliminate the need for manual testing in some scenarios, but it will never eliminate the need for QA.”
— Chris Marsh, Director of Technology, AKQA
Marsh points out that automation becomes one tool in a QA engineer’s toolkit rather than a wholesale replacement for the role. Unit tests are relatively cheap to write and execute, making them strong candidates for automation. Integration tests and UI tests, however, often require more manual oversight because they touch complex, context-sensitive user interactions that are difficult to fully script in advance.
The Zero-Defect Trap
Traditional QA philosophy often aims to eliminate every defect before a release goes live. While that goal is well-intentioned, it carries a real cost: delaying the feedback loop with actual users and reducing return on investment. No production software is truly defect-free, and chasing that standard can prevent teams from shipping working features that deliver real value.
QA engineers need to be embedded in the build pipeline from the start, advising on quality standards across the entire project lifecycle rather than acting as a final gate at the end of the process. Shifting quality thinking earlier — sometimes called “shift-left testing” — allows teams to catch issues when they are cheapest to fix.
A Test Is Only as Good as Its Design
Automation raises a fundamental dependency: the quality of your automated tests determines the quality of your feedback. An automated suite that tests the wrong things, or that has grown stale as the codebase evolved, provides a false sense of confidence rather than genuine assurance.
“Because technology development is a complex, dynamic process, automated QA is doomed to fail unless someone is able to make sure that the tests are current — or new bugs and vulnerabilities will not be detected.”
— Greg Hoffer, VP of Engineering, Globalscape
Hoffer highlights an important failure mode: a serious security vulnerability can slip through an automated QA process if no test was ever written to check for that specific condition. Automated tests only cover the scenarios their authors anticipated. Novel bugs, edge cases, and security issues that emerge from unexpected usage patterns require human investigation to uncover.
There is also a usability dimension that pure automation cannot address. A fully automated test suite can confirm that software behaves exactly as specified while that software remains entirely unusable by real people. Automated checks validate functional correctness against predefined criteria — they cannot assess whether the product actually meets human needs or delivers a coherent user experience.
“Automated QA, continuous integration (CI), and continuous deployment (CD) are all great advances in the efficiency of DevOps. But we should not expect them to be perfect. It is still incumbent on the developer community to be vigilant.”
— Greg Hoffer, VP of Engineering, Globalscape
QA May Actually Become More Strategic, Not Less Relevant
Rather than shrinking the QA function, automation is reshaping it. As CI/CD pipelines absorb routine regression testing, QA engineers can focus on higher-value work: exploratory testing, risk analysis, test strategy, and quality advocacy across the organization.
“As confidence in CI and automation increases, there is a very likely scenario of customers using Continuous Delivery for selective parts of their applications, although it still is not something that is completely reliable.”
— Rupinder Singh, Senior Vice President, Expert Services, Software AG
Singh observes that as automation handles manual test cycles, the QA role gains visibility and importance in technical communities. The engineer who can design a sustainable, maintainable automated test strategy — and know when to supplement it with human judgment — becomes a critical asset rather than a legacy overhead.
Human Creativity Remains the Missing Ingredient
Automated tests are excellent at verifying that known paths through an application still work and that new code has not broken existing behavior. What they cannot do is invent new test scenarios, reason about unexpected user behavior, or ask the question: “What happens if someone uses this feature in a way we never anticipated?”
“It still takes human creativity and ingenuity to explore those paths, and then write automated tests against expected outputs. Companies must — and should — continue to employ QA teams, and they need to invest in training and software licenses for the automation platforms.”
— Mark Doyle, Software Architect, Collabroscape
Doyle also identifies a compounding benefit of well-designed automated testing: when failed tests automatically create entries in a defect tracking system, QA engineers can use that data to build more comprehensive and targeted test plans over time. Automation feeds information back to humans, who then improve the automation — a virtuous cycle that requires active human participation to sustain.
Practical Benefits of Test Automation in a QA-Led Pipeline
- Faster build validation: Running an automated suite before manual QA begins saves engineers from investing time in a broken build.
- Consistent regression coverage: Automated tests reliably re-check existing functionality every time code changes, catching regressions that manual spot-checking might miss.
- Freed capacity for exploratory work: Removing routine test execution from human queues allows QA engineers to focus on complex, judgment-intensive scenarios.
- Automatic defect logging: Integration between CI pipelines and issue trackers reduces manual overhead and ensures failures are captured immediately.
- More stable software over time: Consistent automated coverage enforces quality gates that accumulate stability across releases.
The Bottom Line
Test automation is a force multiplier for QA, not a replacement for it. It handles repetitive, well-defined test scenarios at scale and speed no human team can match. But the strategic design of what to test, the maintenance of test suites as software evolves, the evaluation of usability, and the exploration of unanticipated failure modes all require human expertise.
DevOps teams that treat automation as a substitute for QA judgment risk shipping software that passes every test yet still fails its users. The more mature approach is to invest in QA engineers who understand automation deeply — and know precisely where automation ends and human insight must begin.