The role of QA in modern engineering organisations is evolving rapidly. Manual testing gates are giving way to automated quality pipelines, and QA engineers are becoming quality coaches who embed quality practices across the entire development lifecycle. This guide covers how to lead a QA team through this transformation while maintaining the quality standards your users depend on.
Defining a Modern Test Strategy
A modern test strategy is built on the testing pyramid - many fast unit tests at the base, fewer integration tests in the middle, and a small number of end-to-end tests at the top. Each layer serves a different purpose and catches different categories of defects. Your role is to ensure the right balance across these layers and that the overall strategy provides confidence in every release.
Define what each layer of testing should cover and who is responsible. Unit tests are typically written by developers. Integration tests may be a shared responsibility. End-to-end tests covering critical user journeys are often where QA engineers focus their automation efforts. Clear ownership prevents gaps and duplication.
Include non-functional testing in your strategy. Performance testing, accessibility testing, security testing, and chaos testing are often overlooked but critical for a complete quality picture. Determine which of these your QA team owns directly and which are collaborative efforts with specialised teams.
- Build a testing pyramid with appropriate balance across unit, integration, and end-to-end tests
- Define clear ownership for each testing layer between developers and QA engineers
- Include non-functional testing - performance, accessibility, security - in your quality strategy
- Regularly review test suite health: coverage, execution time, and flakiness metrics
Investing in Test Automation
Test automation is the most impactful investment a QA team can make. Automated tests provide fast, reliable, repeatable feedback that scales with your codebase. Prioritise automating regression tests for critical user journeys first - these provide the highest return on investment by catching regressions before they reach users.
Choose automation frameworks and tools that align with your technology stack and your team's skills. If your application is web-based, tools like Playwright or Cypress provide excellent developer experience. For API testing, consider tools that integrate with your CI/CD pipeline. For mobile, platform-specific frameworks like XCTest and Espresso offer the most reliable results.
Treat test automation code with the same quality standards as production code. Apply code review, maintain clear documentation, use design patterns for maintainability, and refactor regularly. Unmaintained test automation quickly becomes a liability - flaky tests that are ignored or disabled provide false confidence.
Building Quality Into the Development Process
Quality is not a phase that happens after development - it is a continuous practice woven throughout the development lifecycle. Your QA team's role should shift from finding defects after code is written to preventing defects through earlier involvement in design, planning, and development.
Involve QA engineers in story refinement and design discussions. Their perspective on edge cases, error scenarios, and testability can prevent entire categories of defects from being introduced. This shift-left approach is far more effective than catching defects after implementation.
Establish quality metrics that the entire team owns, not just QA. Defect escape rate, customer-reported bugs, test coverage, and release rollback frequency are quality indicators that reflect the team's collective commitment to quality. When quality metrics are solely the QA team's responsibility, developers feel absolved of quality ownership.
Evolving the QA Engineer Role
The traditional QA role - manual testing against test cases - is becoming increasingly obsolete. Modern QA engineers need skills in automation, programming, CI/CD, and quality coaching. Help your team develop these skills through training, mentoring, and gradually shifting their work from manual testing to automation and quality engineering.
Position QA engineers as quality advocates and coaches within product teams. Rather than being the last line of defence, they should be enabling developers to write better tests, reviewing test strategies, and identifying quality risks early in the development process. This consultative role is more impactful and more sustainable than manual testing.
Be transparent with your team about the evolution of the role. Some QA engineers will embrace the shift to automation and quality engineering with enthusiasm. Others may struggle with the transition. Provide support, training, and time for the transition, but be honest about the direction the role is heading.
Key Takeaways
- Build a testing pyramid with clear ownership and balance across unit, integration, and end-to-end tests
- Prioritise automation of critical user journeys and treat test code with production-quality standards
- Shift quality left by involving QA in design discussions and story refinement
- Evolve QA engineers from manual testers to quality coaches and automation engineers
- Make quality metrics a shared team responsibility, not solely the QA team's concern
Frequently Asked Questions
- Do we still need a dedicated QA team?
- It depends on your organisation's maturity and context. Some high-performing teams have eliminated dedicated QA roles, with developers owning all testing. Others maintain QA engineers who focus on automation frameworks, quality coaching, and exploratory testing. The key question is not whether QA should exist but what form it should take - the traditional manual testing gate is rarely the right answer in modern software development.
- How do I handle resistance from QA engineers who prefer manual testing?
- Acknowledge their expertise while being honest about industry trends. Provide learning resources, pair programming with automation-skilled engineers, and start with small automation projects that build confidence. Give them time to develop new skills, but be clear that the direction is non-negotiable. Some engineers will thrive with the transition; others may ultimately be better suited to roles at organisations with different quality approaches.
- How do I deal with flaky tests that undermine confidence in automation?
- Treat flaky tests as high-priority bugs. Track flakiness rates, quarantine flaky tests so they do not block CI, and fix them promptly. Common causes include timing issues, test interdependence, and environmental instability. Invest in test infrastructure that provides consistent, isolated environments and establish coding standards that prevent common causes of flakiness.
Access Quality Engineering Resources
Explore our quality engineering tools including test strategy templates, automation ROI calculators, and quality metrics dashboards for engineering managers.
Learn More