testing
Installation
SKILL.md
Testing
A test is worth what it would catch. Imagine the plausible broken versions of the code (a < that should be <=, a dropped rule, swapped operands, a missing reset, an unrounded cent) and make sure at least one test fails for each. A suite that only checks the happy path passes against almost all of them. Read the catalog for the kind of code under test:
| The code under test | Read |
|---|---|
| Thresholds, formulas, parsers, text, dates, money, comparators, state machines, time-based and stateful code, delays and timeouts, orchestration | CATALOG.md |
The shape of the suite, integration tests against real Postgres in containers, data isolation, async workflows across modules, architecture and contract tests, end-to-end tests (writing and running them in a browser or on a device is the e2e-testing skill) |
INTEGRATION.md |
| Creating or evaluating a lint rule or detector, including its contract, fixtures, real-code labels, fuzzing and paired comparisons | lint-rule-authoring |
| Authorized test-first development: one public behavior slice, the intended failing check, minimal implementation and existing persistence/callback exceptions | TDD.md |
| An interactive CLI or TUI: reuse its harness, capture before acting, deterministic prompt waits, transcripts, inspector environment and profile evidence | CLI-HARNESS.md |
| Generate or maintain a project verification skill: launch, Doctor, drive, evidence, cleanup, feature maps and source/live drift | PROJECT-VERIFICATION.md |
| Create or maintain code-linked formal checks: tool choice, atomicity, scope, counterexample replay, mutation sensitivity and sync commits | FORMAL-VERIFICATION.md |
Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]