Testing AI agents: mock the model or use the real API?
Split AI agent tests into 4 layers: pure code, tools, the real model, and review. Use mocks without false confidence, then run a small real-model eval.
|
I'm Samuel Fajreldines I am a specialist in the entire JavaScript and TypeScript ecosystem (including Node.js, React, Angular and Vue.js) I am expert in AI and in creating AI integrated solutions I am expert in DevOps and Serverless Architecture (AWS, Google Cloud and Azure) I am expert in PHP and its frameworks (such as Codeigniter and Laravel). |
|
Samuel Fajreldines I am a specialist in the entire JavaScript and TypeScript ecosystem (including Node.js, React, Angular and Vue.js) I am expert in AI and in creating AI integrated solutions I am expert in DevOps and Serverless Architecture (AWS, Google Cloud and Azure) I am expert in PHP and its frameworks (such as Codeigniter and Laravel).
|
Split AI agent tests into 4 layers: pure code, tools, the real model, and review. Use mocks without false confidence, then run a small real-model eval.
Test a TypeScript MCP server with a stdio client, Vitest, and Inspector. Catch broken schemas, missing tools, and errors before CI.
Build an AI software engineer portfolio that shows the problem, architecture, tests, failures, operations, and decisions behind a project.
Learn when AI agents need durable execution, checkpoints, queues, or workflows to resume safely after failures and retries in production with clear trade-offs.
Compare Graphiti, vector RAG, and PostgreSQL for AI agent memory. Separate truth, retrieval, history, and verification before production decisions at scale.