For the past ten-plus years this has been a hard question to answer. The answer usually came back to team composition, product type and system architecture. But frankly, with AI moving as fast as it is, the answer today is very different from two years ago. Let's walk through this interesting shift step by step.
The myth: are these really different roles?
By definition, test automation is part of SQA (Software Quality Assurance). So why do so many people treat them as two separate roles? The reason is simple: from the outside, the day-to-day work of the two roles really does look quite different.
- SQA may spend more time designing test cases and running tests
- Test automation engineers spend more time in code, building test frameworks and writing automated tests But does that distinction really make sense?
SQA: a fuzzy definition
The SQA role changes with the environment:
- Startups: usually wear many hats, covering everything from product testing to user experience evaluation
- Large enterprises: may focus more on process management and risk assessment
- Different product types: B2B and B2C products demand very different things from SQA
SQA is more than testing. It involves:
- Product testing
- User experience evaluation
- Process management
- Risk assessment
The real core of test automation
Test automation is more than writing code. It requires:
- Understanding system architecture
- Knowledge of network protocols
- Working with databases
- Familiarity with testing patterns
- Performance optimisation skills
Technical skills matter, but broad IT knowledge and problem-solving ability matter more.
How we did it two years ago (before AI)
Before AI became widespread, we looked at the following to decide whether test automation made sense:
- How stable the product requirements were
- How predictable the test scenarios were
- The team's technical capability
- Return on investment (in time)
A new view in the age of AI
AI tools have greatly lowered the barrier to test automation. The emphasis has shifted from programming skills to the ability to use AI tools.
This shift has brought the following changes:
- A lower technical barrier to test automation
- Easier test case generation
- Less maintenance complexity
- Better prospects for test coverage
Core skills for SQA today
In the age of AI, we should look for testers with these qualities:
- A solid grounding in testing theory: understands different testing methods and strategies
- Strong test case design: can design effective test scenarios
- Flexible use of AI tools: makes good use of a range of AI assistants
- A habit of continuous learning: willing to adapt to new technologies and tools
Conclusion
The traditional distinction between SQA engineers and test automation engineers matters less and less in the age of AI. What matters is finding people who can adapt to a fast-changing technical environment and who have the right testing mindset.
Rather than getting stuck on job titles, focus on an engineer's ability to learn, ability to adapt and commitment to quality. In this AI-driven era, the most valuable people are testing professionals who can use all kinds of tools flexibly and keep evolving.
When choosing testing talent, look at their potential and willingness to learn rather than rigid role definitions. That is how you build a quality assurance team that actually works in a fast-changing technical environment.