Testing
Use for every Kortix test task, behavior change, bug fix, refactor, API route change...
Install
npx skills add kortix-ai/suna --skill testing -g -a claude-code -y- Repository
- kortix-ai/suna20.3k
- Category
- Testing
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use for every Kortix test task, behavior change, bug fix, refactor, API route change, CLI change, SDK change, browser journey, test failure, coverage question, local benchmark, or testing infrastructure change. Enforce the single local-first runner, black-box flow contracts, package-local SDK tests, browser-only Playwright tests, and real input/output verification.
Testing
During development, never run a full suite or a whole package's tests.
Run T0 (tsc, lint) for the packages you touched, the test files that cover
your change named one by one (pnpm --filter <pkg> test <file>, or one flow
with pnpm test -- --id <ID>), and the change itself through its real
surface. Seconds, not minutes. Running a whole package's suite to check one
file is the anti-pattern, and on a Mac every package test script refuses it
(exit 2, scripts/test-guard.mjs) unless you name files or pass
-- -t <name>. The full
suite runs once, at Promote to Production, on the release pull request into
prod: it is the only gate (AGENTS.md, "Testing philosophy").
Keep tests small and isolated. Every test file runs standalone in seconds. When the test that covers your change takes more than ~10 s, or needs setup unrelated to it, split it into a smaller isolated test in the same change. Fake the clock; never wait on real time. A test that breaks on a refactor with no bug is deleted, not updated.
The repository-level command is pnpm test; on a Mac only its targeted modes
run (--id, --domain, --db-only <filter>, --sdk-only).
Read tests/README.md before changing the runner or adding a product flow. Read
the sdk skill before editing the SDK.
