# Cairo Testing

> Provides Cairo smart-contract testing strategy with progressive references for snforge unit, integration, fuzz, and fork tests.

- Skill: `cartridge-gg/cairo-testing` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add cartridge-gg/cairo-testing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cartridge-gg/cairo-testing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- License: Apache-2.0
- Author: cartridge-gg (https://skillmd.com/u/cartridge-gg)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cartridge-gg/cairo-testing

---


# Cairo Testing

Use this entrypoint to choose test scope and sequence, then load specific patterns from references.

## When to Use

- Building unit, integration, fuzz, or fork tests.
- Designing regression tests for known findings.
- Validating event and failure semantics.

## When NOT to Use

- Contract architecture decisions (`cairo-contract-authoring`).
- Performance tuning (`cairo-optimization`).
- Deployment operations (`cairo-toolchain`).

## Quick Start

1. Add unit tests for all state-mutating selectors.
2. Add negative tests for auth/input failures.
3. Add at least one fuzz/property test for core invariants.
4. Convert fixed findings into permanent regression tests.
5. Run `cairo-auditor`; fix or explicitly triage/document new findings first, then add regression tests before merge.

## Workflow

- Main testing flow: [default workflow](workflows/default.md)

## References

- Detailed testing reference: [legacy reference](references/legacy-full.md)
- Module index: [references index](references/README.md)
- Security regression recipes: `../datasets/distilled/test-recipes/`