Quality
Testing your agent.
Test the contract, not just the code. Your agent is safe to publish only when the manifest, schemas, auth flow, and user-visible chat path all work together.
Testing layers.
Use small tests for local code, then run full contract checks before every submission.
| Layer | What to verify |
|---|---|
| Unit | Provider client mapping, input validation, output shape, error shape. |
| Contract | Manifest parses, OpenAPI exposes intended tools, x-orchet metadata is valid. |
| OAuth | Connect, refresh, disconnect, and expanded scopes. |
| End-to-end | User asks in Orchet chat, connect card appears if needed, tool executes, result renders. |
Local and deployed checks.
Run these before submission and again after deploy.
SHELL
npm test orchet-agent validate orchet-agent validate \ --manifest-url https://weather-demo.example.com/.well-known/agent.json curl -fsS https://weather-demo.example.com/health curl -fsS https://weather-demo.example.com/openapi.json
Production smoke checklist.
After approval, test like a user. Ask for the capability in chat, connect the app if prompted, run one read-only action, run one write preview if supported, confirm it, and verify the provider reflects the change.