Agent Sandbox Registry

python-sdk

Testing & Definition of Done

docs/en/guide/testing-e2e.md

Testing & Definition of Done

How the Python SDK (agent-sandbox) and the in-sandbox server (agent-sandbox-server) are verified end to end, and the rules that decide when a change counts as done.

中文版: ../../zh/guide/testing-e2e.md

Verification layers

Layer Tool Real components? Credentials Typical time
Unit tests make test (pytest in client-sdk/tests, server-sdk/tests) No (mocks) none seconds
Real-cloud E2E make e2e Yes: real platform, envd, in-sandbox server .env or environment ~8 min
E2E incl. slow cases make e2e-all Yes same longer

Only the real-cloud layer can close the "E2E" item of the Definition of Done.

Running the E2E suite

cp .env.example .env     # fill in real values; .env is gitignored
make e2e                 # fast path
make e2e-all             # + slow tests
make e2e-cleanup         # dry-run janitor for leftovers; ARGS=--yes deletes

Without credentials every test is skipped with an explicit reason, and the unit CI never collects the suite. Every sandbox created by the suite is tagged and removed in finalizers; scripts/e2e-cleanup.py handles runs that were killed hard. Details, markers and guarantees are in e2e/README.md. Product defects found by the suite are recorded as strict xfails and listed in e2e/KNOWN-ISSUES.md.

Definition of Done

A change is done when all of the following hold:

  1. Unit tests, lint and scripts/check-repo-health.sh pass.
  2. The feature was exercised against real components (make e2e or a targeted E2E case), not only mocks.
  3. Docs are complete in English and Chinese and a CHANGELOG entry exists.
  4. Large changes are recorded as an ADR under .agents/notes/ with the correct status.
  5. Evidence (commands, results, resource cleanup) is stored in .agents/evidence/verify/<date>-<topic>.md, with no secrets.
  6. No sandbox is leaked.

The full rules and the ADR and evidence templates: .agents/notes/DEFINITION-OF-DONE.md.

Cloud example practice

Outside the test suite, the walkthrough that runs the example scripts on the default provider is Cloud end-to-end practice. The Agents API case is not on that page; see Agents API.