Files
zeekayandHanzo Dev e0e84f7808 The Python SDK's tests run, it calls /v1, and it can keep memory in Base
- A rebrand wrote "Hanzo Agents" into identifiers, so the conftest did not
  parse and no test ran.
- The client built {url}/api/v1; the control plane serves /v1. Notes append
  /ui to the base instead of rewriting its first /v1.
- BaseMemory stands where MemoryClient stands; pass it to Agent as `store`. It
  binds to the running execution, so scope ids resolve as the control plane
  resolves them, and a read without a scope walks workflow, session, actor and
  global.
- The web3 extension declares eth-account as an extra, and stops exporting two
  modules that import packages this SDK does not have.
- A heartbeat test waits for the state it asserts instead of sleeping.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-11 04:10:34 -07:00
..

Test Layout

  • tests/ contains the supported open-source regression suite. These tests run in CI and cover the SDK surface that ships publicly.
  • legacy_tests/ preserves the original internal suite. Those tests exercise tightly coupled infrastructure (MCP, remote services, etc.) and are excluded from the default run. Execute them manually via pytest legacy_tests when the required services are available.

Fixtures live in tests/conftest.py and are shared by both suites.