Skip to content
Back to skills

Minimal

ASecurity

Guidelines for when and how to use mocks in tests

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
developmentjavascripttypescriptpythonrustgojavarubyphpapidatabase

Works with

  • api

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add snoodleboot-io/prompticorn --skill minimal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Minimal?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Minimal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/snoodleboot-io-minimal-bb7108b6/badge)](https://www.skillsdirectory.com/skills/snoodleboot-io-minimal-bb7108b6)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: test-mocking-rules
description: Guidelines for when and how to use mocks in tests
languages: [python, typescript, javascript, go, rust, java, csharp, php, ruby]
subagents: [test/unit, test/integration]
tools_needed: []
---

## Mocking Rules

### When to Mock
- Mock only at process boundaries:
  - Database connections
  - Network calls (HTTP, external APIs)
  - Filesystem operations
  - Time/date functions
  - Random number generation

### What NOT to Mock
- **Never mock the thing under test**
- **Never mock internal helpers** — test them through the public interface
- **Never mock your own database** in integration tests

### Consistency
- Use the mock library from core-conventions.md consistently
- Follow the same mocking patterns across the codebase

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…