| name | scenarios |
| description | This skill should be used when validating features end-to-end without mocks, testing integrations, or when "scenario test", "e2e test", or "no mocks" are mentioned. |
| metadata | {"version":"1.0.0"} |
Scenario Testing
End-to-end validation using real dependencies, no mocks ever.
<when_to_use>
- End-to-end feature validation
- Integration testing across services
- Proof programs demonstrating behavior
- Real-world workflow testing
- API contract verification
- Authentication flow validation
NOT for: unit testing, mock testing, performance benchmarking, load testing
</when_to_use>
<iron_law>
NO MOCKS EVER.
Truth hierarchy:
- Scenarios โ real dependencies, actual behavior
- Unit tests โ isolated logic, synthetic inputs
- Mocks โ assumptions about how things work
Mocks test your assumptions, not reality. When mocks pass but production fails, the mock lied. When scenarios fail, reality spoke.
Test against real databases, real APIs, real services. Use test credentials, staging environments, local instances โ but always real implementations.
</iron_law>
<directory_structure>
.scratch/ (gitignored)
Throwaway test scripts for quick validation. Self-contained, runnable, disposable.
CRITICAL: Verify .scratch/ in .gitignore before first use.
scenarios.jsonl (committed)
Successful scenario patterns documented as JSONL. One scenario per line, each a complete JSON object.
