testing-patterns

testing-patterns is a skill for Claude Code from softspark/ai-toolkit. It costs 52 tokens per session (1,453 once invoked), scanned A, original, Apache-2.0.

A guide to organising software tests, including isolated unit tests, integration tests, end-to-end tests, test doubles, coverage, and flaky-test control.

In plain words
What is it for?
Use it when deciding which kind of test to write, arranging test files, using mocks or fixtures, and checking coverage or unreliable tests.
Why use it?
It gives developers a shared structure for writing tests and helps them avoid tests that are hard to trust or maintain.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the ai-toolkit plugin — 115 skills, 44 agents, 14 hooks shipped together

Good fit Use it when deciding which kind of test to write, arranging test files, using mocks or fixtures, and checking coverage or unreliable tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/softspark/ai-toolkit/testing-patterns
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 softspark/ai-toolkit --skill testing-patterns
Clone the repo
git clone --depth 1 https://github.com/softspark/ai-toolkit

Made for: Claude Code.

Or install ai-toolkit, the plugin that ships this one along with the rest of its 115 skills, 44 agents, 14 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.

agentmods badge for testing-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/softspark/ai-toolkit/testing-patterns/github.svg)](https://agentmods.dev/skills/softspark/ai-toolkit/testing-patterns)
Your own site
<a href="https://agentmods.dev/skills/softspark/ai-toolkit/testing-patterns"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/testing-patterns/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for testing-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/softspark/ai-toolkit/testing-patterns"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/testing-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,453 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.01453
Opus 5.5 $0.00021 $0.00581
Sonnet 5.5 $0.00010 $0.00291
Haiku 4.5 $0.00005 $0.00145

Measured 1mo ago against content hash d89d4c5a6ac5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing-patterns 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 1mo ago.

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.

app/skills/testing-patterns/SKILL.md · 130 lines

How it starts

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

Testing Patterns Skill

Test Structure (AAA Pattern)

def test_function_does_expected_thing():
    """Test description explaining what and why."""
    # Arrange - Set up test data and preconditions
    input_data = {"key": "value"}
    expected = "result"

    # Act - Execute the code under test
    result = function_under_test(input_data)

    # Assert - Verify the outcome
    assert result == expected

Test Organization

tests/
├── conftest.py           # Shared fixtures
├── unit/                 # Unit tests (isolated)
│   ├── test_search_core.py
│   └── test_utils.py
├── integration/          # Integration tests
│   └── test_api.py
└── e2e/                  # End-to-end tests
    └── test_workflow.py

Quality Targets

Metric Target
Coverage >70% overall
New code 100%
Core modules >80%
No flaky tests 0

Validation contract regressions

Mirrored validators can agree on a generated snapshot while disagreeing on real inputs. Execute the same accepted/rejected fixtures against the real backend validator and the client evaluator. Include N/N+1 boundaries, collection/item limits, omitted/null/empty/default values, nested paths, conditional branches, hydrated updates versus fresh DTOs, Unicode units and previously valid inputs.

Test the actual HTTP path for malformed input and unchanged persisted state after a pre-write refusal. Test zero transport calls for a local refusal, normal transport for a valid payload, and field correction/resubmission. Run deterministic-generation and reviewed-exclusion checks separately from behavioral parity. A schema/rule count is inventory, not assertion coverage.

For operation semantics and runtime mismatches, read reference/input-validation.md from the installed security-patterns skill. Resolve the skill through the current client's catalog; directory names may carry an adapter-specific prefix.

Language-Specific References

Language Reference Key Topics
Python reference/python-pytest.md Fixtures, mocking, parametrize, markers, conftest, running tests
TypeScript reference/typescript-vitest.md Vitest/Jest, React Testing Library, mocking, running tests
PHP reference/php-phpunit.md PHPUnit test cases, mocking, running tests
Go reference/go-testing.md Table-driven tests, testify mocking, running tests
Flutter/Dart reference/flutter-testing.md Widget tests, unit tests, running tests

Read the full file on GitHub · 130 lines

Files

What ships with it

5 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.

  1. 1mo ago Changed · +19 lines d89d4c5a6ac5
  2. 1mo ago First seen · 111 lines · 52 tokens per session scan A 838e60336ca9

Subscribe to this mod's changes

testing-patterns is a skill published in the GitHub repository softspark/ai-toolkit (180 stars, last pushed 4d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,453 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

testing-strategy

Comprehensive testing expertise across unit, integration, and e2e tests. Covers pytest, Vitest, Jest, Go testing, Playwright, Cypress. Test pyramids, TDD workflow, mocking patterns, coverage targets, property-based testing, snapshot testing, parameterized tests, fixtures, CI integration. Use when writing tests…

medy-gribkov/arcana · 83 tokens

webapp-testing

Write and run comprehensive web app tests — unit, integration, E2E with Playwright/Cypress, and visual regression.

inbharatai/claude-skills · 29 tokens

testing-strategy

Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.

w95/awesome-claude-corporate-skills · 56 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

qa-testing-strategy

Designs risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, choosing test layers, or establishing release criteria.

vasilyu1983/AI-Agents-public · 37 tokens

proof-strategy

Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".

tonone-ai/tonone · 53 tokens