Testing

How to test skills you write, and how the Splice repository tests itself.

Testing a skill

Tools are plain modules with a default export, so most tests call them directly with Node's test runner:

node --test tests/*.test.ts

• Network tools: replace globalThis.fetch in the test with a stub and assert on the requests your tool makes (see skills/github/tests in the repository).
• Capability tools: pass a stub context — { capability: async (name, args) => result } — and assert on the capability name and arguments. The host behaviour is tested by Splice itself.
• Schemas: splice publish --dry-run validates the manifest and every schema; add examples (examples/*.json with tool, input and, where deterministic, output) for documentation.

Run the tool in the real sandbox before publishing by installing it into a project from a local registry (npm run registry:dev in a source checkout, then splice publish --registry local). Permission denials then behave exactly as in production.

How the repository is tested

Unit tests may stub provider HTTP only inside test files (the fetch test seam of the data layer); production code has no mock or fixture path. Live tests fail if any result contains a configured key.