TMMi Test Strategy

TMMi Test Maturity Testing Test Strategy

Overview

Draft and maintain a project or programme test strategy aligned to TMMi: objectives, test levels, approach, entry/exit criteria, and resources.

Example Conversation

You: We’re starting a new programme and need a test strategy aligned to TMMi. Can you draft one with test levels, entry/exit criteria, and resource outline?
Agent: I’ll draft a test strategy covering: test objectives and scope; test levels (unit, integration, system, acceptance) and how they’re sequenced; test approach (e.g. risk-based, techniques); entry and exit criteria per level; and resources (roles, effort, environment). I’ll align the structure to TMMi expectations for a managed test process.
You: We have three streams—backend, frontend, and mobile—and want risk-based testing with system test exit at 95% pass and no critical open defects.
Agent: I’ve added the three streams to the scope, set a risk-based test approach, and defined system test exit criteria: 95% planned tests executed and passed, no critical or high defects open. The strategy is in test-strategy.md.

Sample Output Excerpt

Excerpt from a test strategy produced with this skill.

Test levels and approach

Level	Objective	Entry criteria	Exit criteria
Unit	Verify components	Code complete, build green	All unit tests pass
Integration	Verify interfaces	Components integrated	Integration tests pass, no blocking defects
System	Verify end-to-end behaviour	System build deployed	95% tests pass, no critical/high open
Acceptance	Validate against user needs	System test complete	Acceptance criteria met, sign-off

Test approach: Risk-based; prioritise high-risk areas and critical user journeys. Test design and execution are documented and traceable to requirements.

Getting Started

Add your source materials to the project workspace, then activate the TMMi Test Strategy skill. The agent will guide you through the process step by step.