Why does this skill forbid the use of mocks?

Mocks test your assumptions about how a system works, not how it actually behaves. By testing against real dependencies, you avoid 'false passes' where the mock succeeds but production fails due to unexpected real-world behavior.

What is the purpose of the .scratch/ directory?

It serves as a temporary playground for self-contained scripts used for quick validation or debugging. These scripts are automatically gitignored to prevent cluttering the main repository with local test logic.

How do I save a successful test pattern?

Once a behavior is verified in a scratch script, you document the steps, setup, and expected outcome in the scenarios.jsonl file to create a permanent, executable record of the system's requirements.

Can I use this skill with production data?

No. The skill rules strictly prohibit testing against production data. You should always use staging environments, local instances, or dedicated test credentials to maintain safety.

Scenario Testing

Name: Scenario Testing
Author: outfitter-dev

byoutfitter-dev

•

Security & Testing

Validates software features through end-to-end testing against real dependencies without using mocks or stubs.

About

The Scenario Testing skill enforces a 'no mocks' philosophy for Claude Code, ensuring that your software is validated against actual databases, APIs, and services rather than assumptions. It provides a structured workflow for creating disposable proof-of-concept scripts in a gitignored scratch directory before documenting successful, reproducible patterns in a centralized scenarios.jsonl file. By prioritizing real-world behavior over synthetic inputs, this skill helps developers catch integration failures early and build a library of proven system interactions.

Key Features

Strict 'no mocks' policy to ensure testing against real system behavior
Persistent scenarios.jsonl format for documenting regression patterns
Structured workflow: Write, Execute, Document, and Cleanup
Standardized .scratch/ directory for disposable, self-contained validation scripts
Automated .gitignore verification to protect local test environments
18 GitHub stars

Use Cases

Creating isolated proof programs to reproduce and debug production issues
Verifying API contracts and database integrity across microservices
Validating complex authentication flows like JWT or OAuth against real services

About

Key Features

Strict 'no mocks' policy to ensure testing against real system behavior
Persistent scenarios.jsonl format for documenting regression patterns
Structured workflow: Write, Execute, Document, and Cleanup
Standardized .scratch/ directory for disposable, self-contained validation scripts
Automated .gitignore verification to protect local test environments
18 GitHub stars

Use Cases

Creating isolated proof programs to reproduce and debug production issues
Verifying API contracts and database integrity across microservices
Validating complex authentication flows like JWT or OAuth against real services