observability-testing
Installation
SKILL.md
Observability Testing
Test that your code produces correct logs — not just that it runs.
Logs are your only window into production behavior. If critical paths don't log correctly, you're flying blind during incidents. This skill teaches you to verify structured log output as part of your test suite.
When to use: Testing error logging with context, audit trails, monitoring integration, log level policy enforcement, any code where observability matters.
When not to use: Pure business logic tests, UI components, tests where logging is incidental not critical.
Rationalizations (Do Not Skip)
| Rationalization | Why It's Wrong | Required Action |
|---|---|---|
| "Logs are side effects, not behavior" | Incorrect logs = blind in production | Assert log output as first-class behavior |
| "I can see logs when I run it" | Manual inspection doesn't scale | Automate with mock logger assertions |
| "Any log level is fine" | Wrong levels = alert fatigue or missed incidents | Enforce log level policy |
| "Context isn't important" | Context-free logs are useless for debugging | Assert required context fields |