Testing doubles

Overview

Polyglot supports deterministic tests at two main seams.

• use fake drivers when you want to bypass HTTP and drive the runtime directly
• use MockHttpDriver when you want to keep transport and provider adapter behavior in play

Pick the shallowest seam that still exercises the behavior you care about.

The same rule applies to all three operation families. Inference and embeddings ship reusable fake drivers in test support. For Decision, implement the small CanProcessDecisionRequest contract as an application-local fake or inject a MockHttpDriver client when the TypeSafe wire adapter is under test.

FakeInferenceDriver

FakeInferenceDriver lives in packages/polyglot/tests/Support.

Use it when you want to test:

• Inference request execution without real HTTP
• retry and event behavior around raw inference responses
• streaming assembly from queued PartialInferenceDelta batches

It supports:

• queued InferenceResponse objects
• queued streaming delta batches
• callback-driven sync or streaming behavior when the test needs custom logic

FakeEmbeddingsDriver

FakeEmbeddingsDriver also lives in packages/polyglot/tests/Support.

Use it when you want to test:

• Embeddings and PendingEmbeddings behavior without real HTTP
• memoization and runtime delegation
• event dispatch around completed embeddings responses

It supports:

• queued EmbeddingsResponse objects
• callback-driven response generation from EmbeddingsRequest
• request recording through handleCalls and requests

Minimal example:

use Cognesy\Polyglot\Embeddings\Data\EmbeddingsResponse;
use Cognesy\Polyglot\Embeddings\Data\Vector;
use Cognesy\Polyglot\Tests\Support\FakeEmbeddingsDriver;

$driver = new FakeEmbeddingsDriver([
    new EmbeddingsResponse([new Vector(values: [0.1, 0.2], id: 0)]),
]);
// @doctest id="4fef"

MockHttpDriver

Use MockHttpDriver when the HTTP layer still matters.

This is the right seam for:

• provider adapter tests
• request body and header assertions
• golden tests around provider-specific payload shapes
• error-path coverage that depends on real HTTP response objects

If the test is really about transport or adapter behavior, keep the mock HTTP path. If it is about runtime behavior above transport, prefer the fake drivers.

For Decision, build the runtime with DecisionRuntime::fromConfig(..., httpClient: $httpClient) to cover the TypeSafe request and response adapters without a live API call. See Decision errors and testing for the full Decision test matrix and opt-in live smoke command.

Which One To Use

Use this rule of thumb:

• FakeInferenceDriver for most deterministic inference tests
• FakeEmbeddingsDriver for most deterministic embeddings tests
• an application-local CanProcessDecisionRequest fake for Decision runtime behavior
• MockHttpDriver for transport and provider adapter coverage