Prove It Works (No-Mock Testing) FAQs

Question 1

Can I use this skill for unit testing?

Accepted Answer

While you can, this skill is specifically optimized for integration and scenario testing. Traditional unit tests for isolated logic are better handled through standard testing frameworks.

Question 2

What is the purpose of the .scratch directory?

Accepted Answer

The .scratch directory is a git-ignored space for throwaway scripts used for quick validation, debugging, or exploring API behavior without cluttering the main codebase with temporary files.

Question 3

How is the scenarios.jsonl file used?

Accepted Answer

It serves as a committed record of proven system behaviors and regression indicators, acting as an executable specification that documents how features should behave under real-world conditions.

Question 4

Is it safe to use with production data?

Accepted Answer

No. The skill rules strictly mandate using test credentials, staging environments, or local instances to prevent accidental data loss or production outages.

Question 5

Why does this skill prohibit mocks?

Accepted Answer

Mocks test your assumptions about how a system works, whereas this skill tests reality. Testing against real databases and APIs ensures that your code works in production-like environments rather than relying on potentially incorrect mocks.

Prove It Works (No-Mock Testing)

Key Features

Use Cases

Prove It Works (No-Mock Testing)

Key Features

Use Cases