javascript-testing-patterns

javascript-testing-patterns is a skill for Claude Code from HermeticOrmus/claude-code-game-development. It costs 63 tokens per session (6,351 once invoked), scanned B, a copy of javascript-testing-patterns, MIT.

A guide to testing JavaScript and TypeScript applications with Jest, Vitest, and Testing Library. It covers unit tests for small pieces of code, integration tests for connected parts, and end-to-end tests for complete user flows.

In plain words
What is it for?
Use it to write tests, configure test infrastructure, mock APIs, test frontend components, and run tests in continuous integration pipelines.
Why use it?
It helps you catch regressions, test external dependencies safely, and build a repeatable test setup. It also explains TDD, where tests are written before the implementation.

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 import { logger } from '../utils/logger';.

Part of the javascript-typescript plugin — 4 skills, 1 command, 2 agents shipped together

Good fit Use it to write tests, configure test infrastructure, mock APIs, test frontend components, and run tests in continuous integration pipelines.

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/HermeticOrmus/claude-code-game-development
agentmods
npx agentmods add skills/hermeticormus/claude-code-game-development/javascript-testing-patterns

Made for: Claude Code.

Or install javascript-typescript, the plugin that ships this one along with the rest of its 4 skills, 1 command, 2 agents.

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 javascript-testing-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/hermeticormus/claude-code-game-development/javascript-testing-patterns/github.svg)](https://agentmods.dev/skills/hermeticormus/claude-code-game-development/javascript-testing-patterns)
Your own site
<a href="https://agentmods.dev/skills/hermeticormus/claude-code-game-development/javascript-testing-patterns"><img src="https://agentmods.dev/badge/skills/hermeticormus/claude-code-game-development/javascript-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 javascript-testing-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/hermeticormus/claude-code-game-development/javascript-testing-patterns"><img src="https://agentmods.dev/badge/skills/hermeticormus/claude-code-game-development/javascript-testing-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,351 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00063 $0.06351
Opus 5.5 $0.00025 $0.02540
Sonnet 5.5 $0.00013 $0.01270
Haiku 4.5 $0.00006 $0.00635

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

Security

Grade B, and why

javascript-testing-patterns scanned grade B with 1 finding 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

const response = await fetch('https://api.example.com/users', { method: 'POST',
Origin

This is a copy

100% identical to javascript-testing-patterns — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/javascript-typescript/skills/javascript-testing-patterns/SKILL.md · 1,026 lines

How it starts

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

JavaScript Testing Patterns

Comprehensive guide for implementing robust testing strategies in JavaScript/TypeScript applications using modern testing frameworks and best practices.

When to Use This Skill

  • Setting up test infrastructure for new projects
  • Writing unit tests for functions and classes
  • Creating integration tests for APIs and services
  • Implementing end-to-end tests for user flows
  • Mocking external dependencies and APIs
  • Testing React, Vue, or other frontend components
  • Implementing test-driven development (TDD)
  • Setting up continuous testing in CI/CD pipelines

Testing Frameworks

Jest - Full-Featured Testing Framework

Setup:

// jest.config.ts
import type { Config } from 'jest';

const config: Config = {
  preset: 'ts-jest',
  testEnvironment: 'node',
  roots: ['<rootDir>/src'],
  testMatch: ['**/__tests__/**/*.ts', '**/?(*.)+(spec|test).ts'],
  collectCoverageFrom: [
    'src/**/*.ts',
    '!src/**/*.d.ts',
    '!src/**/*.interface.ts',
  ],
  coverageThreshold: {
    global: {
      branches: 80,
      functions: 80,
      lines: 80,
      statements: 80,
    },
  },
  setupFilesAfterEnv: ['<rootDir>/src/test/setup.ts'],
};

export default config;

Vitest - Fast, Vite-Native Testing

Setup:

// vitest.config.ts
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    globals: true,
    environment: 'node',
    coverage: {
      provider: 'v8',
      reporter: ['text', 'json', 'html'],
      exclude: ['**/*.d.ts', '**/*.config.ts', '**/dist/**'],
    },
    setupFiles: ['./src/test/setup.ts'],
  },
});

Unit Testing Patterns

Pattern 1: Testing Pure Functions

// utils/calculator.ts
export function add(a: number, b: number): number {
  return a + b;
}

export function divide(a: number, b: number): number {
  if (b === 0) {
    throw new Error('Division by zero');
  }
  return a / b;
}

// utils/calculator.test.ts
import { describe, it, expect } from 'vitest';
import { add, divide } from './calculator';

describe('Calculator', () => {
  describe('add', () => {
    it('should add two positive numbers', () => {
      expect(add(2, 3)).toBe(5);
    });

    it('should add negative numbers', () => {
      expect(add(-2, -3)).toBe(-5);
    });

    it('should handle zero', () => {
      expect(add(0, 5)).toBe(5);
      expect(add(5, 0)).toBe(5);
    });
  });

  describe('divide', () => {
    it('should divide two numbers', () => {
      expect(divide(10, 2)).toBe(5);
    });

    it('should handle decimal results', () => {
      expect(divide(5, 2)).toBe(2.5);
    });

    it('should throw error when dividing by zero', () => {
      expect(() => divide(10, 0)).toThrow('Division by zero');
    });
  });
});

Read the full file on GitHub · 1,026 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. 1mo ago First seen · 1,026 lines · 63 tokens per session scan B 91bd0860da65

Subscribe to this mod's changes

javascript-testing-patterns is a skill published in the GitHub repository HermeticOrmus/claude-code-game-development (73 stars, last pushed 21d ago), licensed MIT. It adds 63 tokens to every session and 6,351 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (sends data to an external url). It is 100% identical to javascript-testing-patterns, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

tests-run

Execute Unity tests (EditMode or PlayMode) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.

IvanMurzak/Unity-MCP · 68 tokens

web-game-performance-and-testing

Use when working on any browser game (Phaser, PixiJS, three.js, Babylon.js, PlayCanvas, Excalibur, KAPLAY) - requestAnimationFrame with clamped delta and visibility pause, zero-allocation frame loops, measuring in DevTools, bundle and asset size budgets, Vitest with seeded RNG and injected time, and a seeded…

makifbaysal/tasktrooper · 87 tokens

smoke-check

Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.

striderZA/OpenCodeGameStudios · 61 tokens

python-pytest-ops

Modern pytest patterns for effective testing.

0xDarkMatter/claude-mods · 44 tokens

test-generator

Generate test templates for unit tests, integration tests, and UI tests using Swift Testing and XCTest. Use when adding tests to iOS/macOS apps.

rshankras/claude-code-apple-skills · 33 tokens

testing-python

Stratégie de Tests Python 3.14+. Use when writing tests, reviewing test coverage, or setting up testing.

TheBeardedBearSAS/claude-craft · 28 tokens