Guide 05 · Test Strategy
Test Strategy
The high-level testing approach: manual and automated checks, tools and the test pyramid.
Start with these short notes and examples. This guide will be expanded over time.
What is a Test Strategy?
A Test Strategy is a high-level document that provides the overall testing approach. It guides test design, the balance of manual and automated testing, and the standards used for testing activities.
A strategy can apply across an organisation or to a particular project. The Test Plan turns that approach into a concrete scope, schedule, set of resources and responsibilities.
Example · CRM project
- Regression: automate repeatable checks on existing CRM features.
- New features: use manual verification and exploratory testing alongside suitable automated checks.
- Performance: test the CRM under high user load.
- Security: check access controls and protection of customer data.
- Tools and frameworks: specify choices such as Selenium for browser automation and JMeter for performance testing.
These are example choices; the actual approach depends on the product, risks and team.
Test pyramid · Unit, Integration & E2E
The test pyramid is a guideline for balancing automated checks. Start with many small, fast tests and use fewer broad tests where they add useful coverage.
- Unit tests · Foundation
- Check a small component in isolation. CRM example: validate the rules for a customer email address.
- Integration tests · Connections
- Check that components work together. CRM example: verify that the customer service saves a customer record to the database.
- E2E tests · Complete journeys
- Check a workflow across the application. CRM example: sign in, add a customer and find the saved record in the customer list.
The pyramid does not prescribe fixed percentages. Choose the balance according to risk, feedback speed and maintenance cost.