Skip to content

testing.md

Latest commit

 

History

History
54 lines (40 loc) · 1.99 KB

testing.md

File metadata and controls

54 lines (40 loc) · 1.99 KB
Raw

Testing and verification

Complete gate

pnpm install --frozen-lockfile
pnpm check

The gate runs:

  • Biome format verification;
  • TypeScript project-reference type checking and build;
  • Vitest unit, lifecycle, HTTP/SSE, Adapter fixture, OTel, and catalog tests;
  • Go SDK tests;
  • Python SDK standard-library tests;
  • generated Schema drift check;
  • custom public-data scan and Secretlint.

Provider contract tests

Adapter tests use loopback HTTP fixture servers with fictional model, execution, and artifact IDs. They verify request paths, SSE or polling lifecycle, tool argument deltas, usage mapping, result artifacts, and terminal events. They do not use real provider credentials or call public provider services.

Container check

docker build -t model-runtime-api:test .
docker run --rm -d --name model-runtime-test \
  -p 127.0.0.1:14320:4320 \
  -e MODEL_RUNTIME_HOST=0.0.0.0 model-runtime-api:test
curl --fail http://127.0.0.1:14320/v1/runtime
docker rm -f model-runtime-test

Use a task-specific container name and loopback port. The default image includes Mock only.

Public-data checks

The repository scan rejects common credential formats, private keys, bearer tokens, private IPs, local user paths, and internal-looking domains. Secretlint provides a second independent scan. GitHub Secret Scanning and Push Protection remain repository-level controls.

No scanner proves that prose or fixtures are safe. Review every public diff for private architecture, provider configuration, customer content, prices, routing weights, and local paths before push.

Documentation media checks

pnpm check:docs validates Markdown and HTML image references, requires a provenance sidecar for every bitmap, caps each image at 512 KiB, and caps all documentation bitmaps at 2 MiB. Generated images also require manual inspection and an independent no-text image-read result. Exact technical relationships remain deterministic and are separately rendered with Mermaid during release review.