New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Testing Test Strategy

by dzhalaevd in dzhalaevd/Donatello

Use as the lead skill when choosing what backend tests to write, reviewing test plans, or balancing unit, integration, API, concurrency, and E2E coverage

Apache-2.0Auto-check passedTesting & QA

Install Testing Test Strategy

skills CLI
$ npx skills add dzhalaevd/Donatello --skill testing-test-strategy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dzhalaevd/Donatello testing-test-strategy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dzhalaevd/Donatello.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing-test-strategy .claude/skills/testing-test-strategy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
testing-test-strategy
GitHub stars
135
Token cost
~1.7k tokens
SKILL.md length
750 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Use as the lead skill when choosing what backend tests to write, reviewing test plans, or balancing unit, integration, API, concurrency, and E2E coverage

  • Works in 4 steps: bug protection; → resistance to safe refactoring; → fast feedback; → …
  • Tasks that involve Test strategy
  • SKILL.md covers Purpose, Skill Routing, Product Fit and Agent Mindset, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Testing Test Strategy is an agent skill from dzhalaevd/Donatello. Use as the lead skill when choosing what backend tests to write, reviewing test plans, or balancing unit, integration, API, concurrency, and E2E coverage

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test strategy, Test generation and End-to-end testing. It works with Python and pytest. The repository describes itself as: Make Dating Great Again. An open source dating platform. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Test strategy
  • Tasks that involve Test generation
  • Tasks that involve End-to-end testing

Example prompts

  • “/testing-test-strategy”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. bug protection;
  2. resistance to safe refactoring;
  3. fast feedback;
  4. maintenance cost.

What it can do on your machine

Read from SKILL.md and the folder at commit b57816e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Testing Test Strategy loads about 1.7k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 750 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dzhalaevd/Donatello at commit b57816e, republished under its Apache-2.0 licence (© dzhalaevd). 750 words, ~1,713 tokens.

Download SKILL.mdSave it as .claude/skills/testing-test-strategy/SKILL.md (or your agent's skills folder).
name
testing-test-strategy
description
Use as the lead skill when choosing what backend tests to write, reviewing test plans, or balancing unit, integration, API, concurrency, and E2E coverage

Backend Test Strategy

Purpose

Help an agent choose a valuable backend test suite. The goal is confidence, safe refactoring, and readable tests, not maximum coverage.

Use this skill when the user asks to:

  • choose a testing strategy;
  • explain what tests are needed for a feature;
  • review whether a test suite has the right balance;
  • reduce fragile, slow, or low-value tests.

Skill Routing

Choose the lead skill by the primary risk, then add supporting skills for tooling or workflow.

User needLead skillSupporting skills
Decide what tests are neededtesting-test-strategyunit-testing, integration-testing, concurrency_fuzzing_testing, testing-pytest
Isolated Python logic, validation, transformations, simple async function awaited onceunit-testingtesting-pytest
Real database, repository, transaction, migration, API flow, or multiple componentsintegration-testingtesting-pytest
Multiple workers/tasks/threads, asyncio.Queue, shared state, locks, cancellation, backpressure, lost updates, order-dependent failuresconcurrency_fuzzing_testingintegration-testing, testing-pytest
Runnable pytest syntax, fixtures, parametrization, mocks, pytest-httpx, dirty-equalsthe relevant level skilltesting-pytest
Production change should be test-firstthe relevant level skilltest-driven-development, testing-pytest

Async alone is not a concurrency-fuzzing signal. An async function with controlled dependencies and no competing task is usually a unit test. Concurrency fuzzing becomes the lead when correctness depends on interleaving between concurrent operations.

Product Fit

For this project, tests should protect meaningful user outcomes and trust. Prefer tests that verify compatibility, transparency, safety, and offline-meeting flows over tests that only defend internal plumbing.

Do not optimize test plans around engagement mechanics, gamified loops, or retention-only behavior.

Agent Mindset

  • Tests should verify behavior, not implementation details.
  • Tests should support development, not exist solely for coverage metrics.
  • A good test is understandable, independent, and resilient to refactoring.
  • Prefer sociable tests when they give greater confidence at a reasonable cost.
  • Use solitary/unit tests for pure functions, isolated complex logic, and many edge cases.
  • Do not test components that do not belong to the application, such as the database engine, SQL engine, framework, or third-party SDK internals.
  • Do not turn tests into a custom abstraction framework on top of pytest.

Choosing Test Level

Before writing tests, identify the observable behavior and the smallest public interface that can verify it.

Unit Tests

Choose unit tests when:

  • a single unit of behavior is being verified;
  • the code is fast and has no real I/O;
  • the logic is pure or nearly pure;
  • many edge cases need coverage.

A unit is a unit of behavior, not necessarily one class or function.

Integration Tests

Choose integration tests when:

  • interactions between components must be verified;
  • repositories, transactions, migrations, serialization, or database state matter;
  • behavior should be tested close to production;
  • unit tests do not provide enough confidence.

Use an isolated test database. Never use production data or production infrastructure.

Show full SKILL.md (312 more words)Show less
API and E2E Tests

Choose API or E2E tests when:

  • a key user or API scenario is verified end to end;
  • the public interface is the important contract;
  • the scenario is business-critical.

Keep E2E tests few. They are slower, costlier to maintain, and worse at localizing failures.

Use this as a default:

  • unit tests for pure business logic, validation, calculations, and complex branching;
  • integration tests for repositories, database behavior, transactions, and component interaction;
  • API/E2E tests for key routes and business flows.

If a service has little isolated business logic, it is fine to have more integration/API tests and fewer unit tests.

Coverage

Coverage is a signal, not a goal.

Judge tests by:

  1. bug protection;
  2. resistance to safe refactoring;
  3. fast feedback;
  4. maintenance cost.

A small suite that catches real regressions is better than 100% coverage made of brittle tests.

Review Checklist

  • Tests verify behavior, not implementation.
  • Test names describe scenarios clearly.
  • Arrange / Act / Assert is visible.
  • Each test has one main Act.
  • There are no hidden branches or if statements inside tests.
  • Tests do not depend on execution order.
  • Mocks are justified and limited to real boundaries.
  • Important failures and edge cases are covered.
  • Tests survive safe refactoring.
  • Tests are fast enough for their level.
  • Coverage is not the only reason a test exists.

Response Format

When the user asks for a strategy:

  1. Break the feature into observable behaviors.
  2. Assign unit, integration, API, or E2E levels.
  3. State what to mock and why.
  4. Give the smallest useful scenario list.

When the user asks for a review:

  1. Lead with the main risks.
  2. Point out brittle or redundant tests.
  3. Suggest a concrete restructuring.
  4. Provide an improved example if helpful.

Short Rule

Write more confidence, not more tests.

A test should answer: if this fails, did user-visible or business behavior actually break?

© dzhalaevd, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/testing-test-strategy of dzhalaevd/Donatello.

Open the folder on GitHubat commit b57816e

Compare with similar skills

Testing Test Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Testing Test Strategy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing Test Strategy this skilldzhalaevd/Donatello135—~1.7kAutomated safety check: PassApache-2.0
Python Testing Patternsjh941213/my-cc-harness12617 repos~5.4kAutomated safety check: PassNone
Testing Patternssoftspark/ai-toolkit179—~1.6kAutomated safety check: PassApache-2.0
Python Testingathola/claude-night-market342—~800Automated safety check: PassMIT
Adk Verify Snippetsgoogle/adk-python22k—~1.4kAutomated safety check: PassApache-2.0
Hermetic Python Unit TestsdimensionalOS/dimos4.6k—~1.4kAutomated safety check: PassCustom licence

Similar skills

  • Python Testing Patterns

    jh941213/my-cc-harness

    Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development.

    126 GitHub starsUsed in 17 repos~5.4k tokens
    Testing & QAAuto-check passed

  • Testing Patterns

    softspark/ai-toolkit

    Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage.

    179 GitHub stars~1.6k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Python Testing

    athola/claude-night-market

    Python testing patterns with pytest, fixtures, TDD, mocking, async and integration tests.

    342 GitHub stars~800 tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Adk Verify Snippets

    google/adk-python

    Official

    Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail…

    22k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Hermetic Python Unit Tests

    dimensionalOS/dimos

    Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.

    4.6k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Designing Tests

    CloudAI-X/claude-workflow-v2

    Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub starsUsed in 1 repo~1.5k tokens
    Testing & QAAuto-check passed

More from dzhalaevd/Donatello

All 15 skills in this repo

  • API And Interface Design

    dzhalaevd/Donatello

    Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 9 repos~2.6k tokens
    Auto-check passed

  • Documentation And Adrs

    dzhalaevd/Donatello

    Records decisions and documentation. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 8 repos~2.4k tokens
    Auto-check: notes

  • CI CD And Automation

    dzhalaevd/Donatello

    Automates CI/CD pipeline setup. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 7 repos~2.7k tokens
    Auto-check: notes

  • Deprecation And Migration

    dzhalaevd/Donatello

    Manages deprecation and migration. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 7 repos~3.1k tokens
    Auto-check passed

  • Observability And Instrumentation

    dzhalaevd/Donatello

    Instruments code so production behavior is visible and diagnosable.

    135 GitHub starsUsed in 5 repos~2.7k tokens
    Auto-check passed

  • Shipping And Launch

    dzhalaevd/Donatello

    Prepares production launches. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 5 repos~2.5k tokens
    Auto-check passed

Works with

Categories

Questions about Testing Test Strategy

What does Testing Test Strategy do?

Use as the lead skill when choosing what backend tests to write, reviewing test plans, or balancing unit, integration, API, concurrency, and E2E coverage. Testing Test Strategy is an agent skill from dzhalaevd/Donatello.

When should I use Testing Test Strategy?

Testing Test Strategy fits situations like: tasks that involve Test strategy; tasks that involve Test generation; tasks that involve End-to-end testing.

How do I install Testing Test Strategy in Claude Code?

Run `npx skills add dzhalaevd/Donatello --skill testing-test-strategy -a claude-code`. Or copy the skill folder (.agents/skills/testing-test-strategy in dzhalaevd/Donatello) into .claude/skills/testing-test-strategy in your project. Claude Code loads it when a task matches its description.

How do I install Testing Test Strategy in Codex?

Run `npx skills add dzhalaevd/Donatello --skill testing-test-strategy -a codex`. Or copy the skill folder (.agents/skills/testing-test-strategy in dzhalaevd/Donatello) into .agents/skills/testing-test-strategy in your project. Codex loads it when a task matches its description.

Can I use Testing Test Strategy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dzhalaevd/Donatello --skill testing-test-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-test-strategy, .gemini/skills/testing-test-strategy, .github/skills/testing-test-strategy and .opencode/skills/testing-test-strategy in your project.

What does Testing Test Strategy need to run?

SKILL.md names no scripts, command-line tools or credentials: Testing Test Strategy is instructions for the agent only. Our summary lists: Python 3.

Does Testing Test Strategy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Testing Test Strategy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Testing Test Strategy use?

Testing Test Strategy is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing Test Strategy use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Testing Test Strategy?

Skills that share tags, products or a category with Testing Test Strategy: Python Testing Patterns (jh941213/my-cc-harness, 126 stars), Testing Patterns (softspark/ai-toolkit, 179 stars), Python Testing (athola/claude-night-market, 342 stars) and Adk Verify Snippets (google/adk-python, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing Test Strategy?

dzhalaevd (a GitHub user) maintains it in dzhalaevd/Donatello, which has 135 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 3, 2026.

Source: dzhalaevd/Donatello on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.