smithery.ai

cairo-test-organization

Explain Cairo test organization for unit vs integration tests, tests directory layout, and shared helpers; use when a request involves structuring tests across files or crates in Cairo.

First seen Apr 22, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,261 B
  • docs SUMMARY.md 216 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Cairo Test Organization

Overview

Explain how to structure unit and integration tests in Cairo projects.

Quick Use

  • Read references/test-organization.md before answering.
  • Put unit tests alongside code in src with #[cfg(test)].
  • Put integration tests in a top-level tests/ directory.

Response Checklist

  • Unit tests can access private functions via module scoping.
  • Integration tests compile as separate crates per file and use the public API.
  • Use tests/lib.cairo to make the tests folder a single crate with shared helpers.

Example Requests

  • "Where do integration tests live in Cairo projects?"
  • "How do I share helpers across integration tests?"
  • "Can unit tests call private functions?"

Cairo by Example