playbooks

home / skills / sandraschi / advanced-memory-mcp / testing-strategy-guide

testing-strategy-guide skill

/skills/technical/testing-strategy-guide

This skill helps you design and implement a comprehensive test strategy covering unit, integration, and automation practices for reliable software.

npx playbooks add skill sandraschi/advanced-memory-mcp --skill testing-strategy-guide

Review the files below or copy the command above to add this skill to your agents.

Files (11)
SKILL.md
2.3 KB
---
name: testing-strategy-guide
description: Test automation expert covering unit tests, integration tests, TDD, and testing best practices
license: Proprietary
---

# Testing Strategy Guide
> **Status**: ✅ Research complete
> **Last validated**: 2025-11-08
> **Confidence**: 🟡 Medium — Research-backed testing playbook – review semi-annually

## How to use this skill
1. Begin with [modules/core-guidance.md](modules/core-guidance.md) to capture context and risk profile.
2. Design test portfolio using [modules/test-pyramid-and-planning.md](modules/test-pyramid-and-planning.md).
3. Build sustainable automation with [modules/automation-frameworks.md](modules/automation-frameworks.md).
4. Cover non-functional requirements via [modules/non-functional-testing.md](modules/non-functional-testing.md).
5. Integrate into CI and monitor via [modules/ci-integration-and-observability.md](modules/ci-integration-and-observability.md).
6. Govern quality metrics through [modules/quality-metrics-and-governance.md](modules/quality-metrics-and-governance.md).
7. Record future improvements in [modules/known-gaps.md](modules/known-gaps.md) and revisit [modules/research-checklist.md](modules/research-checklist.md) twice a year.

## Module overview
- [Core guidance](modules/core-guidance.md) — intake, risk matrix, stakeholder alignment.
- [Test pyramid & planning](modules/test-pyramid-and-planning.md) — strategy, coverage, prioritization.
- [Automation frameworks](modules/automation-frameworks.md) — tooling, architecture, maintenance.
- [Non-functional testing](modules/non-functional-testing.md) — performance, security, accessibility, resilience.
- [CI integration & observability](modules/ci-integration-and-observability.md) — pipelines, flake reduction, analytics.
- [Quality metrics & governance](modules/quality-metrics-and-governance.md) — KPIs, dashboards, process control.
- [Known gaps](modules/known-gaps.md) — research backlog.
- [Research checklist](modules/research-checklist.md) — semi-annual refresh plan.

## Research status
- Testing strategy reflects Google/ThoughtWorks guidance plus recent automation standards.
- Next review due 2026-05-01 or earlier if major framework updates occur.
- Known gaps track AI-assisted testing and chaos engineering maturity tasks awaiting deeper research.

Overview

This skill is a practical testing strategy guide from a test automation expert covering unit tests, integration tests, TDD, and testing best practices. It translates risk-driven planning into a sustainable automated test portfolio and CI integration plan. The playbook is research-backed and designed for semi-annual review and continuous improvement.

How this skill works

Start by capturing context, business risk, and stakeholder priorities to define test objectives. Use the test-pyramid approach to balance unit, integration, and end-to-end coverage and select automation frameworks and architecture that minimize maintenance. Expand the plan to include non-functional testing, CI integration, observability, and governance with KPIs and a process for tracking known gaps and research items.

When to use it

  • When establishing or revising an organization-wide testing strategy
  • When designing a new automation framework or refactoring tests
  • Before adding large new features to ensure appropriate coverage
  • When integrating testing into CI/CD pipelines and observability
  • When setting quality KPIs and governance for release readiness

Best practices

  • Start with risk and stakeholder alignment to prioritize tests, not with tools
  • Favor fast, deterministic unit tests and targeted integration tests over brittle end-to-end suites
  • Design tests and frameworks for maintainability: clear fixtures, isolation, and reuse
  • Measure quality with objective KPIs (test flakiness, coverage by risk, MTTR) and act on them
  • Integrate non-functional tests (performance, security, accessibility) early and automate where feasible
  • Review and refresh the strategy periodically and track known gaps like AI-assisted testing

Example use cases

  • Create a test portfolio for a microservices product to balance contract, integration, and UI tests
  • Plan migration from brittle UI-driven tests to service-level and contract testing to reduce CI flakiness
  • Define acceptance criteria and TDD workflow for a safety-critical feature with high risk
  • Add performance and resilience checks into the CI pipeline with observability hooks
  • Establish team-level KPIs and governance for release readiness across multiple squads

FAQ

How often should the testing strategy be reviewed?

Review the strategy at least twice a year and after major framework or architecture changes.

What test types should receive the most investment?

Invest most in fast, reliable unit tests and meaningful integration/contract tests; keep end-to-end tests focused and limited.