The Evolution from Quality Assurance to Quality Engineering | Amber Insights #004
- Osarobo Aiguobarueghian
- Aug 7
- 6 min read
By Amber Idumwonyi
Software development has changed dramatically over the last two decades.
Applications are released more frequently. Cloud platforms have transformed infrastructure. DevOps has shortened delivery cycles. Automation has become embedded within development pipelines, and Artificial Intelligence is beginning to reshape how software is designed, developed, tested, and maintained.
Yet one of the most significant changes has happened within the testing profession itself.
The role once commonly described as Quality Assurance (QA) is increasingly evolving into something broader:
Quality Engineering (QE).
This is more than a change in terminology.
It represents a fundamental shift in how organisations think about quality, how testing professionals contribute to delivery, and the skills required to succeed in modern software teams.
From Quality Control to Quality Assurance
Traditionally, software testing was often positioned towards the end of the development lifecycle.
Requirements were defined.
Software was designed and developed.
The completed product was then passed to a testing team responsible for validating functionality and identifying defects.
Within this model, testers provided an essential quality-control function. They examined what had been built and identified where the product did not behave as expected.
As software delivery matured, organisations increasingly recognised a limitation with this approach:
Discovering quality problems at the end of development is very different from preventing them throughout development.
This contributed to a broader emphasis on Quality Assurance.
Rather than concentrating exclusively on detecting defects in completed software, QA introduced greater attention to the processes, standards, practices, and controls used to produce quality software.
But the industry continued to evolve.
And so did the role of the tester.
The Emergence of Quality Engineering
Quality Engineering takes the evolution further.
Instead of asking:
"How do we test this product?"
Quality Engineering encourages teams to ask:
"How do we engineer quality into this product?"
That difference is significant.
Quality Engineering integrates quality considerations into the technical and delivery practices used throughout software development.
A Quality Engineer may still perform functional testing, exploratory testing, regression testing, and defect investigation.
But the role can extend considerably beyond those activities.
Modern Quality Engineers may contribute to:
Requirements and acceptance criteria.
Testability discussions.
API and integration testing.
Test automation.
Continuous integration and delivery pipelines.
Accessibility.
Performance and resilience.
Test environments and test data.
Service virtualisation and mocking.
Observability and production quality.
Quality metrics and reporting.
Risk analysis.
Release confidence.
The profession has therefore moved beyond simply validating software after it has been built.
Quality Engineers increasingly influence how software is built.
Automation Changed the Profession
Automation has played a major role in this evolution.
There was a time when large regression suites were executed manually before major releases.
As delivery cycles became shorter, this approach became increasingly difficult to scale.
Teams needed faster feedback.
Automated testing helped provide it.
Today, automation can operate across multiple layers of an application, from unit and API testing to user-interface validation, and can be integrated directly into continuous integration and deployment pipelines.
But Quality Engineering should never be reduced to automation.
Being able to write automated tests does not automatically make someone a Quality Engineer.
Automation is a tool.
Quality Engineering is a discipline.
The value comes from understanding what should be tested, where it should be tested, why it matters, and what level of confidence the testing provides.
Automation is a tool. Quality Engineering is a discipline.
A poorly designed automated test suite can execute thousands of tests and still provide very little meaningful assurance.
Engineering judgement remains essential.
DevOps Changed Where Quality Happens
DevOps also changed the relationship between testing and software delivery.
When organisations released software a few times each year, lengthy testing phases were more manageable.
Modern teams may release monthly, weekly, daily, or even multiple times per day.
Quality practices therefore have to operate at the speed of delivery.
Testing cannot simply wait at the end.
Quality checks increasingly become part of the delivery pipeline itself.
Code can be analysed automatically.
Unit and integration tests can execute after changes.
APIs can be validated.
Security checks can run.
Deployment processes can verify environments.
Automated regression suites can provide rapid feedback.
The result is an important shift:
Quality becomes part of the engineering workflow rather than a separate activity surrounding it.
The Quality Engineer as a Technical Partner
Another important evolution concerns the relationship between testers and other engineering disciplines.
A modern Quality Engineer is not simply the person who receives completed functionality from a Developer.
They work alongside Developers.
They collaborate with Business Analysts.
They challenge requirements with Product Owners.
They discuss architecture with technical teams.
They work with DevOps Engineers on environments and pipelines.
They communicate quality risks to delivery leadership.
This requires much more than testing knowledge.
It requires communication, technical understanding, business awareness, critical thinking, and the confidence to influence decisions.
The strongest Quality Engineers I have worked with do not simply report problems.
They help teams understand problems.
They ask why they occurred.
They investigate how they could be prevented.
And they contribute to solutions.
Quality Engineering Does Not Mean Manual Testing Is Dead
Whenever the industry adopts a new term or technology, there is a temptation to declare everything that came before it obsolete.
We have seen this with manual testing.
We have seen it with automation.
And we are beginning to see it again with Artificial Intelligence.
But Quality Engineering is not about replacing human testing with tools.
Exploratory thinking, business understanding, user empathy, investigation, communication, and professional judgement remain enormously important.
Automation can execute predefined checks extremely efficiently.
It cannot automatically determine whether those are the right checks.
A Quality Engineer must understand when automation provides value and when human investigation provides greater insight.
The profession is evolving through the combination of both.
AI Is Beginning the Next Evolution
Quality Engineering is now entering another period of change.
Artificial Intelligence can already assist with activities such as analysing requirements, generating test ideas, producing test data, supporting automation development, summarising defects, and accelerating technical investigation.
The capabilities will continue to develop.
But I believe the fundamental principle remains unchanged.
Technology changes how we perform certain activities.
It does not remove the need to understand why those activities matter.
Quality Engineers who combine testing fundamentals, engineering capability, domain knowledge, critical thinking, and responsible use of AI will be well positioned for this next stage of the profession.
The role is not disappearing.
It is becoming more sophisticated.
What This Evolution Means for Testers
For professionals currently working in software testing, this evolution should not be viewed as a reason to abandon existing skills.
Strong testing fundamentals remain the foundation.
Understanding requirements matters.
Test design matters.
Exploratory testing matters.
Defect investigation matters.
Communication matters.
What changes is the breadth of capability built on top of those foundations.
A tester might learn API testing.
Then automation.
Then CI/CD.
Then accessibility.
Then cloud technologies.
Then AI-assisted testing.
Career development does not require learning everything simultaneously.
It requires a willingness to continue evolving.
That willingness has become one of the most important characteristics of the modern Quality Engineer.
Final Thoughts
The journey from Quality Assurance to Quality Engineering reflects a much larger transformation in software development.
We have moved from testing predominantly at the end of delivery towards embedding quality throughout engineering.
From detecting defects to also preventing them.
From isolated testing teams to multidisciplinary collaboration.
From manual execution alone to intelligent combinations of human testing, automation, pipelines, tooling, and increasingly AI.
But despite all these changes, the purpose remains remarkably consistent:
To help organisations deliver software that people can trust.
The tools will continue to change.
The technologies will continue to change.
The terminology may even change again.
But professionals who understand quality deeply, and know how to engineer it into modern software delivery will continue to play a critical role in building the digital systems on which businesses, governments, and society increasingly depend.
About the Author
Amber Idumwonyi is a Senior Quality Engineering professional with over eight years of experience delivering quality engineering solutions across UK Government, defence, healthcare, and enterprise technology programmes.
She has led Quality Engineering initiatives, developed enterprise Test Strategies, contributed to modern automation and quality practices, spoken at industry conferences, and founded LEMP, an organisation focused on practical technology education, industry experience, mentoring, and career development.
Amber is passionate about Quality Engineering, AI-assisted testing, technical leadership, and developing the next generation of technology professionals.
Comments