What is testing-strategy?

A workflow for deciding what testing a change needs and which test layer should prove it. It covers unit tests for small pieces, integration tests for connected parts, and end-to-end tests that check a complete user flow.

Use it to choose test scope, design scenarios, select unit, integration, E2E, or other test layers, prepare test data and fakes, and define release or CI checks.

It prevents teams from writing the wrong kind of test or leaving important behavior unverified. It also helps define fixtures, mocks, regression checks, smoke tests, CI gates, and verification evidence.

testing-strategy — Skill for Claude Code and Codex by ccoalm

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add ccoalm/ccl-skills --skill testing-strategy

Clone the repo

git clone --depth 1 https://github.com/ccoalm/ccl-skills

Made for: Claude Code, Codex.

Or install ccl-skills, the plugin that ships this one along with the rest of its 33 skills, 4 commands, 7 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ccoalm/ccl-skills/testing-strategy.svg)](https://agentmods.dev/skills/ccoalm/ccl-skills/testing-strategy)

Your own site

<a href="https://agentmods.dev/skills/ccoalm/ccl-skills/testing-strategy"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-skills/testing-strategy.svg" alt="Measured on agentmods" height="20"></a>

Per session 189 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 10,634 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00189	$0.10634
Opus 5	$0.00095	$0.05317
Sonnet 5	$0.00038	$0.02127
Haiku 4.5	$0.00019	$0.01063

Measured 3d ago against content hash 3527e55b44e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

testing-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/client-terminal-ansi-check.py, scripts/client-terminal-ansi-check.test.sh, scripts/lang-basics-ast-check.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/testing-strategy/SKILL.md · 214 lines

How it starts

The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing Strategy

Use this skill when the task is about test scope, test design, verification evidence, CI gates, or deciding which layer should prove behavior. It is stack-agnostic: apply it across Go services, Python services, React web, mobile apps, mini-programs, terminal/CLI/TUI surfaces, APIs, workflows, data/inference features, and product releases.

Skill Routing

Use this skill for test strategy, test pyramid decisions, unit/integration/e2e/scenario boundaries, fixtures, mocks/fakes, regression coverage, and verification evidence. Stack pointers below apply after that choice.
Use go-microservice-dev for Go-specific implementation details.
Use python-service-dev for Python-specific pytest, async test, fixture, fake client, ruff, mypy/pyright, packaging, or migration-test implementation details.
Node runner, mock/fixture, fake timers, stream and cancellation assertions, child-process lifecycle, and packaged-artifact verification must use nodejs-service-dev.
Use app-cross-platform-dev for Flutter unit/widget/integration tests, Android unit/Compose/instrumented tests, iOS unit/UI tests, mobile device smoke, and app release verification.
Use miniapp-product-dev for WeChat/Alipay/Douyin/Baidu mini-program build, developer-tool preview, real-device smoke, host capability verification, review submission, and release checks.
Use web-react-dev for React unit/component/API-client/browser/E2E implementation, browser automation, accessibility checks, and build/deploy smoke.
Use terminal-cli-dev for the terminal interface contract, PTY/ANSI/keyboard rendering, and full-screen text UI testing.
Use llm-inference-integration for LLM/agent/RAG evals, replay sets, prompt/model regression checks, shadow runs, and inference-specific observability.
Use defect-diagnosis first when a test is failing, flaky, or used to reproduce a bug.
Use product-rd-workflow first when testing is part of an end-to-end product delivery plan.
Use product-ui-ux-design for visual hierarchy, interaction, state, accessibility, and design acceptance criteria; use this skill for automated proof and test coverage.
Use test-artifact-management when the ask is about generating structured test cases from a Feishu requirements doc or codebase and delivering them to Feishu Bitable; use this skill for scenario selection and risk matrix before test-artifact-management writes the cases.
For ambiguous "写测试用例" / "write test cases" requests, use this skill first when the user is asking to add, modify, run, or verify test code, E2E/browser/device tests, CI coverage, mocks, or regression evidence. Route to test-artifact-management only when the deliverable is a structured TC artifact, Feishu/Bitable sync, or source-to-TC generation workflow.
For team testing standards, QA norms, CI/harness requirements, or a missing "测试规范" in a product/R&D standards family, use references/rd-testing-standard-template.md as the source-neutral template, then route stack-specific command mechanics to the relevant dev skill.

Read the full file on GitHub · 214 lines

Files

What ships with it

28 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago Changed · +1 lines 3527e55b44e7
7d ago First seen · 213 lines · 189 tokens per session scan A 9efe5339d5bb

Subscribe to this mod's changes

testing-strategy is a skill published in the GitHub repository ccoalm/ccl-skills (6 stars, last pushed today), licensed Apache-2.0. It adds 189 tokens to every session and 10,634 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code E2E testing Testing Unit testing agent-skills ai-agents anthropic codex developer-tools

tdd-workflow

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

affaan-m/ECC · 43 tokens

memstack-development-test-writer

Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.

cwinvestments/memstack · 70 tokens

sd-test

The disciplined test-recipe gate the generic agent runs for the software-delivery TEST step (/foundry:sd-test, step 8). A PROCEDURE — invoke the MERGED foundry-verify.py executor, read the run record's records whose phase == "testrecipe" (unit / integration / e2e), surface the profile's numeric coveragegate and advise…

lukasrepublic/agentic-foundry · 154 tokens

testing-strategy