testing-strategy

testing-strategy is a skill for Claude Code from navraj007in/architecture-cowork-plugin. It costs 19 tokens per session (2,772 once invoked), scanned A, original, Apache-2.0.

A set of rules for organizing software tests, including file names, test folders, test data, mocks, and the Arrange-Act-Assert structure. It covers unit tests, integration tests, and end-to-end tests, which check code parts, connected components, and complete user flows.

In plain words
What is it for?
Use it to choose test locations and names, structure test cases, plan fixtures and mocks, and set coverage expectations for different project stages.
Why use it?
It helps a team write tests in a consistent form and makes the test suite easier to find, understand, and maintain.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is jest.mock('../lib/stripe', () => ({.

Part of the architect plugin — 48 skills, 63 commands, 19 agents, 7 MCP servers shipped together

Good fit Use it to choose test locations and names, structure test cases, plan fixtures and mocks, and set coverage expectations for different project stages.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-plugin
agentmods
npx agentmods add skills/navraj007in/architecture-cowork-plugin/testing-strategy

Made for: Claude Code.

Or install architect, the plugin that ships this one along with the rest of its 48 skills, 63 commands, 19 agents, 7 MCP servers.

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-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/testing-strategy/github.svg)](https://agentmods.dev/skills/navraj007in/architecture-cowork-plugin/testing-strategy)
Your own site
<a href="https://agentmods.dev/skills/navraj007in/architecture-cowork-plugin/testing-strategy"><img src="https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/testing-strategy/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-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/navraj007in/architecture-cowork-plugin/testing-strategy"><img src="https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/testing-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,772 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.02772
Opus 5 $0.00010 $0.01386
Sonnet 5 $0.00004 $0.00554
Haiku 4.5 $0.00002 $0.00277

Measured 8d ago against content hash 3d2b84bbefc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 8d 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.

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

How it starts

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

Testing Strategy Skill

Covers unit, integration, and e2e test patterns for all supported frameworks.

Test File Organization

Folder Structure

  • Unit tests: co-locate with source files
    • src/services/user.tssrc/services/__tests__/user.test.ts (Jest/Vitest)
    • src/services/user.tssrc/services/test_user.py (pytest)
  • Integration tests: separate tests/ directory at project root
    • tests/integration/auth.test.ts
    • tests/integration/database.test.ts
  • E2E tests: separate e2e/ or tests/e2e/ directory
    • e2e/flows/login.test.ts
    • e2e/flows/checkout.test.ts

File Naming Convention

  • Unit: <module>.test.ts or <module>_test.py
  • Integration: <feature>.integration.test.ts or test_<feature>.py
  • E2E: <flow>.e2e.test.ts or test_<flow>_e2e.py

Test Structure: Arrange-Act-Assert

All tests MUST follow AAA pattern:

describe('UserService', () => {
  describe('createUser', () => {
    it('should create a user with valid email and name', () => {
      // ARRANGE: Setup test data, mocks, fixtures
      const email = '[email protected]';
      const name = 'Alice Chen';
      
      // ACT: Call the function under test
      const user = service.createUser(email, name);
      
      // ASSERT: Verify the result
      expect(user.email).toBe(email);
      expect(user.name).toBe(name);
      expect(user.id).toBeDefined();
    });
  });
});

Golden rule: One logical assertion per test (one reason to fail).

Test Naming: Descriptive, Not Clever

❌ BAD:

it('works', () => { ... });
it('user creation 1', () => { ... });

✅ GOOD:

it('should create a user with valid email and return user object with id', () => { ... });
it('should reject email without @ symbol', () => { ... });
it('should hash password before storing in database', () => { ... });

Pattern: should [what happens] [given conditions if not obvious]

Framework-Specific Setup

Node.js / TypeScript (Jest / Vitest)

// jest.config.js
module.exports = {
  preset: 'ts-jest',
  testEnvironment: 'node',
  roots: ['<rootDir>/src', '<rootDir>/tests'],
  testMatch: ['**/__tests__/**/*.ts', '**/*.test.ts'],
  collectCoverageFrom: [
    'src/**/*.ts',
    '!src/**/*.d.ts',
    '!src/index.ts'
  ],
  coverageThreshold: {
    global: {
      branches: 80,
      functions: 80,
      lines: 80,
      statements: 80
    }
  }
};

// tsconfig.test.json
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "jsx": "react",
    "types": ["jest", "node"]
  }
}

Read the full file on GitHub · 444 lines

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. 8d ago First seen · 444 lines · 19 tokens per session scan A 3d2b84bbefc5

Subscribe to this mod's changes

testing-strategy is a skill published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,772 once invoked, about $0.0001 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-09-03.