Description

Adds real integration tests for the MemoryClient platform SDK that hit the live Mem0 API — no mocks, no interceptors. Only a MEM0_API_KEY is needed to run; org/project are auto-resolved via
ping().

Integration test structure:

mem0-ts/src/client/tests/integration/
├── helpers.ts — env gating, client factory, polling helpers
├── initialization.test.ts — ping, error handling (5 tests)
├── crud.test.ts — add, get, getAll, update, delete (10 tests)
├── search.test.ts — search v1, v2, history (3 tests)
├── batch.test.ts — batch update, batch delete (2 tests)
├── management.test.ts — users, project, webhooks (6 tests)
└── feedback-and-export.test.ts — feedback, export (3 tests)

29 tests covering the full API surface:

• Gated by MEM0_API_KEY env var — auto-skips when not set (safe for forks/OSS CI)
• Each test file uses unique UUID-based user IDs for isolation
• Cleanup runs in afterAll regardless of pass/fail
• Handles async memory processing via polling helper

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Unit Test

Run integration tests (real API):
cd mem0-ts
MEM0_API_KEY=your-key npx jest src/client/tests/integration/ --verbose --forceExit

Run unit tests (no API key needed):
cd mem0-ts
pnpm run test:ci

• All 29 integration tests pass against the live Mem0 API
• All 470 existing unit tests pass with no regressions
• Integration tests correctly skip when MEM0_API_KEY is not set

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have checked my code and corrected any misspellings